[JAVASERVERFACES-1997] EL expressions referencing a composite attribute
inside a facet of a composite component are not rendered Created: 17/Mar/11 Updated:
11/Sep/13 Resolved: 08/May/13
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Closed
javaserverfaces
facelets
2.0.3, 2.0.4, 2.1.0
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Environment:
Bug
Mathias Werlitz
Incomplete
None
Not Specified
None
Priority:
Assignee:
Votes:
Not Specified
Not Specified
JDK 1.6, Tomcat 6.0.29
Attachments:
templateELOutputMissing.zip
Issue Links:
Related
is related JAVASERVERFACESto
2839
Status
Whiteboard:
Tags:
Trivial
Unassigned
5
composite component
umbrella task
Closed
size_small importance_medium
composite
Description
Using EL expressions inside a composite component that evaluates a property of a attibute of
this component component and nesting this expression inside a facet of an other composite
component that renders this facet with <cc:renderFacet> does lead to no output. Rendering the
same expression explicitly with a <h:output> component works instead (as a workaround).
Using the same code outside a composite component (in a page) also does work correctly.
The JSF spec (2.1) requires in section 10.3.1 that "The runtime must ensure that EL expressions
that appear in the page without being the right-hand-side of a tag attribute
are treated as if they appeared on the right-hand-side of the value attribute of an <h:outputText
/> element in the http://java.sun.com/jsf/html namespace." This should also work in this case.
Example:
<cc:interface>
<cc:attribute name="model" required="true"/>
</cc:interface>
<cc:implementation>
<myCC:layout>
<f:facet name="content">
direct EL: >#
{cc.attrs.model.data}< outputText: ><h:outputText value="#{cc.attrs.model.data}
" /><
</f:facet>
</myCC:layout>
</cc:implementation>
BTW: MyFaces 2.0.4 has the same issue.
Comments
Comment by Mathias Werlitz [ 17/Mar/11 ]
The example should render 4 times "myData". But the first output fails (is missing) because of
the bug.
Comment by Ed Burns [ 17/Mar/11 ]
Triage.
Comment by Manfred Riem [ 06/Mar/13 ]
Can you verify if this is still an issue with the latest 2.1 release?
Comment by Manfred Riem [ 03/Apr/13 ]
Lowering priority because of no response
Comment by Manfred Riem [ 08/May/13 ]
Closing because of inactivity
Comment by Mathias Werlitz [ 20/Aug/13 ]
Sorry, I was not able to respond here for a long time.
This is still an issue with the latest versions 2.1.25 or 2.2.2.
Please reopen the bug.
Comment by josefreire [ 11/Sep/13 ]
This issue is still present in 2.1.27-SNAPSHOT 20130910-1528.
Could this issue be reopened?
I'll send a simple example (doesn't require managed beans) to the mailing list.
Generated at Tue Feb 09 17:14:30 UTC 2016 using JIRA 6.2.3#6260sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.