Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.6DR#3
-
Fix Version/s: 1.7.1
-
Component/s: None
-
Labels:None
-
Environment:Unknown
-
ICEsoft Forum Reference:
Description
The dataPaginator component is tied to its dataTable by its for attribute being the dataTable's id. But, if those are in a parent dataTable (or possibly a panelSeries or ui:repeat), then apparently data pagination does not work. The inner dataTable and dataPaginator, in this case are virtual components, since they are replicated across each row of the outer dataTable.
Activity
Mark Collette
created issue -
Mark Collette
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Mark Collette [ mark.collette ] |
Mark Collette
made changes -
Description |
The dataPaginator component is tied to its dataTable by its for attribute being the dataTable's id. But, if those are in a panelSeries, ui:repeat, or another parent dataTable, then apparently data pagination does not work. The inner dataTable and dataPaginator, in this case are virtual components, since they are replicated across each row of the outer dataTable. |
The dataPaginator component is tied to its dataTable by its for attribute being the dataTable's id. But, if those are in a parent dataTable (or possibly a panelSeries or ui:repeat), then apparently data pagination does not work. The inner dataTable and dataPaginator, in this case are virtual components, since they are replicated across each row of the outer dataTable. |
Ken Fyten
made changes -
Assignee Priority | P3 |
Ken Fyten
made changes -
Assignee Priority | P3 | |
Assignee | Mark Collette [ mark.collette ] |
Ken Fyten
made changes -
Fix Version/s | 1.7.1 [ 10122 ] | |
Assignee Priority | P2 | |
Assignee | Mark Collette [ mark.collette ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #16806 | Thu Jun 05 10:53:57 MDT 2008 | mark.collette | |
Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/component/src/com/icesoft/faces/component/panelseries/UISeries.java
|
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #16807 | Thu Jun 05 10:57:26 MDT 2008 | mark.collette | |
Files Changed | ||||
MODIFY
/icefaces/branches/icefaces-1.7/icefaces/component/src/com/icesoft/faces/component/panelseries/UISeries.java
|
Mark Collette
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee Priority | P2 | |
Assignee | Mark Collette [ mark.collette ] |
Now our UISeries saves its "first" property when inside any other UISeries, which should cover ice:dataTable, ice:panelSeries, etc.
What that means for this issue, is that when the ice:dataPaginator finds its corresponding ice:dataTable, both inside another ice:dataTable or ice:panelSeries, and it tells the ice:dataTable what page to be on, then that will be independently stored, for each pair, so they won't influence any other pair.
TRUNK
Subversion 16806
icefaces\component\src\com\icesoft\faces\component\panelseries\UISeries.java
ICEfaces 1.7 branch
Subversion 16807
icefaces\component\src\com\icesoft\faces\component\panelseries\UISeries.java