Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.1.1
-
Fix Version/s: 4.2
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ace
-
Assignee Priority:P1
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial
Description
a looping parent component which allows the user to determine what is to be placed in the component attributes .
for example (in the case of ace:panelStack)
<icecore:repeat var="data" value="#{somebean.sequence}" >
<ace:panelStack selectedId="#{data.selectedId}">
<ace:stackPane id="pane1">
.....
</ace:stackPane>
<ace:stackPane id="pane2">
....
</ace:stackPane>
</icecore:repeat>
currently, use of c:forEach is limited in that myfaces causes exception as it requires static data in c:forEach. http://jira.icesoft.org/browse/ICE-10792
A basic repeat tag could have it's own tag handler allowing it to act both like <ui:repeat> and <c:forEach> so that consideration is given while constructing the tree as well as within the tree
for example (in the case of ace:panelStack)
<icecore:repeat var="data" value="#{somebean.sequence}" >
<ace:panelStack selectedId="#{data.selectedId}">
<ace:stackPane id="pane1">
.....
</ace:stackPane>
<ace:stackPane id="pane2">
....
</ace:stackPane>
</icecore:repeat>
currently, use of c:forEach is limited in that myfaces causes exception as it requires static data in c:forEach. http://jira.icesoft.org/browse/ICE-10792
A basic repeat tag could have it's own tag handler allowing it to act both like <ui:repeat> and <c:forEach> so that consideration is given while constructing the tree as well as within the tree
Activity
Field | Original Value | New Value |
---|---|---|
Fix Version/s | 4.2 [ 12870 ] |
Assignee | Mircea Toma [ mircea.toma ] | |
Assignee Priority | P3 [ 10012 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50378 | Mon Feb 06 16:37:08 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() ![]() ![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50379 | Mon Feb 06 16:45:16 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50380 | Mon Feb 06 17:16:00 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() |
Summary | create ace:repeat component which allows components access to repetition and resolved expressions when added to component tree | create icecore:repeat component which allows components access to repetition and resolved expressions when added to component tree |
Affects | Documentation (User Guide, Ref. Guide, etc.) [ 10003 ] |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Description |
a looping parent component which allows the user to determine what is to be placed in the component attributes .
for example (in the case of ace:panelStack) <ace:repeat var="data" value="#{somebean.sequence}" > <ace:panelStack selectedId="#{data.selectedId}"> <ace:stackPane id="pane1"> ..... </ace:stackPane> <ace:stackPane id="pane2"> .... </ace:stackPane> </ace:repeat> currently, use of c:forEach is limited in that myfaces causes exception as it requires static data in c:forEach. http://jira.icesoft.org/browse/ICE-10792 A basic repeat tag could have it's own tag handler allowing it to act both like <ui:repeat> and <c:forEach> so that consideration is given while constructing the tree as well as within the tree |
a looping parent component which allows the user to determine what is to be placed in the component attributes .
for example (in the case of ace:panelStack) <icecore:repeat var="data" value="#{somebean.sequence}" > <ace:panelStack selectedId="#{data.selectedId}"> <ace:stackPane id="pane1"> ..... </ace:stackPane> <ace:stackPane id="pane2"> .... </ace:stackPane> </icecore:repeat> currently, use of c:forEach is limited in that myfaces causes exception as it requires static data in c:forEach. http://jira.icesoft.org/browse/ICE-10792 A basic repeat tag could have it's own tag handler allowing it to act both like <ui:repeat> and <c:forEach> so that consideration is given while constructing the tree as well as within the tree |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50382 | Tue Feb 07 07:09:41 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() ![]() ![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50385 | Wed Feb 08 06:57:29 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50387 | Wed Feb 08 10:45:28 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() ![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50388 | Wed Feb 08 11:07:04 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() |
Security | Private [ 10001 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50543 | Wed Feb 15 15:09:56 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50544 | Wed Feb 15 17:15:41 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50546 | Thu Feb 16 05:29:54 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50566 | Mon Feb 20 12:15:27 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Affects | Documentation (User Guide, Ref. Guide, etc.) [ 10003 ] | Documentation (User Guide, Ref. Guide, etc.),Sample App./Tutorial [ 10003, 10001 ] |
Assignee Priority | P3 [ 10012 ] | P1 [ 10010 ] |
Attachment | textEntryIcecoreRepeat.xhtml [ 22459 ] |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50731 | Thu Feb 23 13:59:57 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() ![]() ![]() ![]() ![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50738 | Fri Feb 24 08:38:56 MST 2017 | carmen.cristurean | |
Files Changed | ||||
![]() |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #50752 | Mon Feb 27 13:27:56 MST 2017 | mircea.toma | |
Files Changed | ||||
![]() |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Implemented icecore:repeat component. It proivides iteration information by means of a additional variable defined by varStatus attribute. It can start iteration at a predefined index by defining the first attribute and/or iterate over a defined number of items when rows attribute is used.