ICEfaces
  1. ICEfaces
  2. ICE-2297

Nested UIData components don't reflect their changed data models

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Invalid
          • Affects Version/s: 1.7DR#2
          • Fix Version/s: None
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            Unknown
          • ICEsoft Forum Reference:
          • Workaround Exists:
            Yes
          • Workaround Description:
            Hide
            Bind the component and programmatically set the value on the component (each time the contents of the component changes):

            dataTable.setValue(list);
            Show
            Bind the component and programmatically set the value on the component (each time the contents of the component changes): dataTable.setValue(list);

            Description

            If you have an outer panelSeries and an inner panelSeries, and they're both showing lists of data, and you dynamically change the lists, it seems that they're somehow keeping around old information that keeps them from properly rendering the new lists.

            This may affects ice:dataTable as well.

              Activity

              Ascending order - Click to sort in descending order
              Mark Collette created issue -
              Philip Breau made changes -
              Field Original Value New Value
              Attachment Test_RowSelectorPanelSeries.war [ 10769 ]
              Mark Collette made changes -
              Assignee Mark Collette [ mark.collette ]
              Ken Fyten made changes -
              Assignee Priority P1
              Philip Breau made changes -
              Summary Problem with nested ice:panelSeries showing changing lists Nested UIData components may not automatically update the UI when the list is changed
              Workaround Description Bind the component and programmatically set the value on the component:

              dataTable.setValue(list);
              Workaround Exists [Yes]
              Philip Breau made changes -
              Workaround Description Bind the component and programmatically set the value on the component:

              dataTable.setValue(list);               		Bind the component and programmatically set the value on the component whenever data has changed and you want to ensure that the UI is updated:

              dataTable.setValue(list);
              Ken Fyten made changes -
              Workaround Description Bind the component and programmatically set the value on the component whenever data has changed and you want to ensure that the UI is updated:

              dataTable.setValue(list);               		Bind the component and programmatically set the value on the component (each time the contents of the component changes):

              dataTable.setValue(list);
              Ken Fyten made changes -
              Fix Version/s 1.7 [ 10080 ]
              Ken Fyten made changes -
              Fix Version/s 1.7Beta1 [ 10121 ]
              Fix Version/s 1.7 [ 10080 ]
              Mark Collette made changes -
              Summary Nested UIData components may not automatically update the UI when the list is changed Nested UIData components don't reflect their changed data models
              Mark Collette made changes -
              Fix Version/s 1.7 [ 10080 ]
              Fix Version/s 1.7Beta1 [ 10121 ]
              Ken Fyten made changes -
              Assignee Priority P1
              Ken Fyten made changes -
              Fix Version/s 1.7 [ 10080 ]
              Assignee Mark Collette [ mark.collette ]
              Ken Fyten made changes -
              Assignee Mark Collette [ mark.collette ]
              Mark Collette made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Invalid [ 6 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]
              Assignee Mark Collette [ mark.collette ]

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Mark Collette
                • Votes:
                  10 Vote for this issue
                  Watchers:
                  9 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: