Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE-4.0.0.GA
-
Fix Version/s: EE-4.0.0.GA
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ICEfaces4 trunk rev# 44025 /44049
Browsers: Firefox 24.5/34, Chrome 40
Server: Tomcat7.0.32/42
-
Assignee Priority:P1
Description
QA test app: http://dev.icesoft.com/svn/repo/qa/trunk/Regression-Icefaces4/Sparkle/Nightly/dataTable
Test page: /tableNestTest.jsf
Test only works as expected if you use paginator before submitting selected rows. If not using paginator, submitted data is not displayed. May have been a regression of fix forICE-10136 ?
Steps:
- go to Table Nesting page: http://localhost:8080/dataTable/views/tableNestTest.jsf
- select one row from the first dataTable at the top of the page, then scroll down and click the Submit button -> selected row fails to render on page under "Selected Rows" section.
- select one row from the same dataTable, or any other, then click on the corresponding paginator of the dataTable to navigate to any other page on that table;
- scroll down and click the Submit button -> this time the "Selected Rows" section contains the selected row.
Test page: /tableNestTest.jsf
Test only works as expected if you use paginator before submitting selected rows. If not using paginator, submitted data is not displayed. May have been a regression of fix for
Steps:
- go to Table Nesting page: http://localhost:8080/dataTable/views/tableNestTest.jsf
- select one row from the first dataTable at the top of the page, then scroll down and click the Submit button -> selected row fails to render on page under "Selected Rows" section.
- select one row from the same dataTable, or any other, then click on the corresponding paginator of the dataTable to navigate to any other page on that table;
- scroll down and click the Submit button -> this time the "Selected Rows" section contains the selected row.
r44072: added a map to associate a client id with a selection state, in order to avoid sharing/overriding states in the case of nested tables, since the transient property that was used to hold this state was being shared by all the nested table instances.
This issue wasn't related to
ICE-10136, as it still occurred after undoing that fix.