ICEfaces
  1. ICEfaces
  2. ICE-7563

MyFaces: Showcase app, ace:draggable/ace:droppable Table demo, Reset doesn't reset source dataTable, just destination one.

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 3.0.RC1
          • Fix Version/s: 3.0.RC2, 3.0
          • Component/s: Sample Apps
          • Labels:
            None
          • Environment:
            ICEfaces 3, Showcase sample app., MyFaces 2.1.3
          • Assignee Priority:
            P2

            Description

            Using the showcase sample app. with MyFaces 2.1.3:

            ace:draggable/droppable:
            Table Integration:
            All browsers: Clicking 'Reset Cart' removes the items from the shopping cart but the table containing the draggable items is not re-populated.
            Confirmed as a MyFaces issue. Looks like the update to reset occurs on the server-side but never makes it as a client update.

            Works fine in Mojarra.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Deryk Sinotte added a comment -

              This is working in my local copy so perhaps the general DataTable state saving change from http://jira.icefaces.org/browse/ICE-7561 also fixed this. However, that change has been reverted by the Component Team to be re-evaluated. If I update to the latest trunk, this and the other problems associated with that change return.

              Show
              Deryk Sinotte added a comment - This is working in my local copy so perhaps the general DataTable state saving change from http://jira.icefaces.org/browse/ICE-7561 also fixed this. However, that change has been reverted by the Component Team to be re-evaluated. If I update to the latest trunk, this and the other problems associated with that change return.
              Hide
              Permalink
              Nils Lundquist added a comment -

              State saving fixes in r26879 didn't resolve this issue, likely the original fix to caching resulted in table state reevaluating and covering up the cause of this bug, so I'm detaching it from that issue for further analysis.

              Show
              Nils Lundquist added a comment - State saving fixes in r26879 didn't resolve this issue, likely the original fix to caching resulted in table state reevaluating and covering up the cause of this bug, so I'm detaching it from that issue for further analysis.
              Hide
              Permalink
              Nils Lundquist added a comment -

              r26883 - Fixed MyFaces table + other component out of sync interaction. MyFaces appears to generate the DataModel for the DataTable lifecycle before the feature being used in this issue has a chance to alter the backing List of the DataTable. Since the DataModel is cached for the life of the component (as was derived from the Mojarra behaviour for getDataModel) we must regenerate the dataModel prerender to catch the changes that have been made. This is required in Mojarra when the DataTable has altered its own backing List during the lifecycle, for example in filtering. The autofiltering the table attempts during its first render is responsible for the state saving change Deryk originally made fixing the issue by continually attempting a filter, and thus regenerating the model.

              Show
              Nils Lundquist added a comment - r26883 - Fixed MyFaces table + other component out of sync interaction. MyFaces appears to generate the DataModel for the DataTable lifecycle before the feature being used in this issue has a chance to alter the backing List of the DataTable. Since the DataModel is cached for the life of the component (as was derived from the Mojarra behaviour for getDataModel) we must regenerate the dataModel prerender to catch the changes that have been made. This is required in Mojarra when the DataTable has altered its own backing List during the lifecycle, for example in filtering. The autofiltering the table attempts during its first render is responsible for the state saving change Deryk originally made fixing the issue by continually attempting a filter, and thus regenerating the model.

                People

                • Assignee:
                  Nils Lundquist
                  Reporter:
                  Ken Fyten
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: