Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.0-Beta2
-
Fix Version/s: 2.0.0
-
Component/s: ICE-Components
-
Labels:None
-
Environment:Windows XP, Glassfish 2.1.1
-
ICEsoft Forum Reference:
Description
This seems like a bug.
Using c:forEach works "fine", except it is not the right thing to use and a modification of the c:forEach source collection will not be reflected after first page view.
Anyone knowing how to solve that, or is there a workaround?
Yannick
Code:
<ui:repeat value="#{GestionDecharges.coursSelTravCollection}" var="ligneActivite" >
<ice:dataTable value="#{ligneActivite.ligneAttributionsAnneeN}"
var="attributionAnneeN">
<ice:column >
<f:facet name="header">
<h:outputLabel value="Nom" style="width: 150px" />
</f:facet>
<h:commandButton value="#{attributionAnneeN.nomEnseignant}" action="#{GestionDecharges.afficherVueProf(attribution.intervenant,GestionDecharges.anacAttributionDisplay)}" styleClass="lien" />
</ice:column>
<ice:column >
<f:facet name="header" >
<h:outputLabel value="Prénom" style="width: 150px"/>
</f:facet>
<h:outputText value="#{attributionAnneeN.prenomEnseignant}" style="width: 150px"/>
</ice:column>
</ice:dataTable>
</ui:repeat>
Issue Links
- is duplicated by
-
ICE-6361
Problems nesting dataTable inside ice:repeat
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue duplicates ICE-6313 [ ICE-6313 ] |
| Assignee | Judy Guglielmin [ judy.guglielmin ] |
| Salesforce Case | [] | |
| Fix Version/s | 2.0.0 [ 10230 ] | |
| Assignee Priority | P1 |
| Link | This issue duplicates ICE-6313 [ ICE-6313 ] |
| Assignee | Judy Guglielmin [ judy.guglielmin ] | Ted Goddard [ ted.goddard ] |
ok, but h:dataTable works in ui:repeat, right? I mean, this is an Icefaces problem, or is it mojarra?
Same problem with Mojarra 2.1.0 (SNAPSHOT b09).
So the question is: is this a mojarra bug or an ICEfaces bug? This is a mojarra bug, since the mojarra datatable renders, but each instance is given the same ID. This means that the page produces visible output, but it would quickly become corrupted as soon as an Ajax update was attempted.
ICEfaces relies on unique IDs during rendering, so shows symptoms sooner.
It may be possible as a workaround to dynamically assign the id on the dataTable where the items in the iteration return a unique ID:
<ice:dataTable id="#
{repeatVar.id}">
Thanks.
Is there a bug report in mojarra's bug tracker?
I'll try the workaround and get back soon.
We have not had a chance yet to create the mojarra bug report. Please do so if it's convenient and include the link here.
I could find those existing bug reports:
http://java.net/jira/browse/JAVASERVERFACES-1830
http://java.net/jira/browse/JAVASERVERFACES-1834
I think the first one is just what you are explaining. Could you confirm this? The second one gives us a hint of a workaround.
Interesting discussion: http://stackoverflow.com/questions/3882147/how-to-refer-to-datatable-parent-within-the-datatable
Regards,
Yannick Majoros
| Fix Version/s | 2.1 [ 10241 ] | |
| Fix Version/s | 2.0.0 [ 10230 ] |
From the java.net bugs, it looks like the mojarra team is aware of the problem. ICEfaces could provide a fix, however, as a new component that functions like h:dataTable but does not introduce the <table> markup. Please contact product.support@icesoft.com if you wish to request a new component for this.
This is not an ICEfaces bug, but could be resolved with a new ICEfaces component with the desired behavior.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Won't Fix [ 2 ] |
| Salesforce Case | [] | |
| Fix Version/s | 2.0.0 [ 10230 ] | |
| Fix Version/s | 2.1 [ 10241 ] | |
| Assignee Priority | P1 |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Testing with h:dataTable shows slightly better behavior: the tables render. However, the behavior is still ultimately flawed since the dataTable components are all assigned the same ID. In the case of ice:dataTable using the compat API DOMContext, duplicate IDs result in DOMContext re-use, causing the component to render on top of itself. JSF will need to be fixed so that ui:repeat behaves as a proper iterative naming container. If this is not implemented in JSF, ICEfaces can provide an ice:repeat that works correctly as an iterative naming container.
This will remain a known issue for ICEfaces 2.0, but an enhanced ice:repeat could be provided upon request to product.support@icesoft.com.