Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-13939

ComponentPostMetadata being cleared on page change causes weird/broken behavior

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.5
    • Fix Version/s: 2.5.1
    • Component/s: User Experience (UX)
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-7767Error tooltips not getting cleared on page change
      KULRICE-11662DocumentService.saveDocument() JPA versus OJB behavior change
      KULRICE-5002clear GlobalVariables after request is processed
      KULRICE-11865Sticky footer adjustments causing too much padding on page change
      KULRICE-8373Delegation/Role caches not being updated after role document delegation change
      KULRICE-6941BusinessObjectDaoOjb.findBySinglePrimaryKey has changed behavior in Rice 2.0
      KULRICE-7623Current page not being highlighted in navigation menu
      KULRICE-12932Spring is autogrowing nested paths causing null objects to be set resulting in STE from eclipseLink
      KULRICE-8072Strange behavior with add lines on collection test view
      KULRICE-1021KR_QRTZ lock table being improperly cleared out by the DatabaseLifeCycle stuff - causing tests to fail
    • Rice Team:
      Framework
    • Rice Module:
      KRAD
    • Application Requirement:
      KC, Rice
    • Sprint:
      Framework 2.5.1 Sprint 2
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes
    • Story Points:
      3

      Description

      Can be reproduced by making a multi paged view with ajaxRetrieval=true dialogs in the view's dialogs property and opening the dialog on the second page. It will see that there is no matching component in the lifecycle when it tries to retrieve it and creates a new reference on the view in ViewLifecycle.setupStandaloneComponentForRefresh <-- THIS NEEDS TO NOT HAPPEN as it breaks functionality (though it may not be immediately apparent without multiple dialogs and component refreshes - although this doesn't need to be added to reproduce the above). Note the correct behavior can be demonstrated/compared if you add the dialog to the page's items instead of the View's dialog items.

        Activity

        Hide
        Martin Taylor (Inactive) added a comment -

        Closing 2.5.1 Development

        Show
        Martin Taylor (Inactive) added a comment - Closing 2.5.1 Development

          People

          • Assignee:
            Nisha Gupta (Inactive)
            Reporter:
            Brian Smith (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Agile

                Structure Helper Panel