[
https://issues.apache.org/jira/browse/MYFACES-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747186#action_12747186
]
Leonardo Uribe commented on MYFACES-2317:
-----------------------------------------
Committed minimal implementation of this tag handler. But the following test
case (nested composite:insertChildren) does not work:
testComposite:compositeInsertChildrenInner
<composite:interface>
</composite:interface>
<composite:implementation>
<h:outputText value="ALFA " />
<composite:insertChildren/>
<h:outputText value="OMEGA " />
</composite:implementation>
testComposite:compositeInsertChildren
<composite:interface>
</composite:interface>
<composite:implementation>
<testComposite:compositeInsertChildrenInner>
<h:outputText value="BETA " />
<composite:insertChildren />
</testComposite:compositeInsertChildrenInner>
</composite:implementation>
test xhtml code
<testComposite:compositeInsertChildren>
<h:outputText value="GAMMA " />
</testComposite:compositeInsertChildren>
Should render:
ALFA BETA GAMMA OMEGA
but render
ALFA OMEGA
The problem is the ordering where composite:insertChildren is called (from most
inner from back). We need a way to call them in inverse order (from out to in).
One option is do the same as h:outputScript and h:outputStylesheet renderers,
suscribe a listener added in PostAddToViewEvent to relocate them, so we can
delegate to that listener the responsibility to order the operations correctly.
This issue is also related to composite:insertChildren
> Implement <composite:insertChildren> tag handler
> ------------------------------------------------
>
> Key: MYFACES-2317
> URL: https://issues.apache.org/jira/browse/MYFACES-2317
> Project: MyFaces Core
> Issue Type: Sub-task
> Components: JSR-314
> Reporter: Leonardo Uribe
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
