[seam-issues] [JBoss JIRA] (JBSEAM-5050) seam:fragment doesn't skip rendering ui:include when seam:fragment rendered attribute is false

[Murat HAZER (JIRA)]

    [ https://issues.jboss.org/browse/JBSEAM-5050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726052#comment-12726052 ] 

Murat HAZER commented on JBSEAM-5050:
-------------------------------------

i'll try to prepare a test case later.

i wrote #{false} just for information, of course real usage is like #{myBean.property} which returns false in this case.

there is a discussion at stackoverflow; http://stackoverflow.com/questions/11989631/skip-executing-uiinclude-when-parent-ui-component-is-not-rendered

2nd answer suggests to use c:if and it really solves the problem. i need to change every seam:fragment tag w/ c:if if we decide to update our application 2.3, this'll be a big problem for us.
                
> seam:fragment doesn't skip rendering ui:include when seam:fragment rendered attribute is false
> ----------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-5050
>                 URL: https://issues.jboss.org/browse/JBSEAM-5050
>             Project: Seam 2
>          Issue Type: Bug
>          Components: JSF Integration
>    Affects Versions: 2.3.0.Final
>            Reporter: Murat HAZER
>
> seam:fragment doesn't skip rendering ui:include when seam:fragment rendered attribute is false
> <seam:fragment rendered="#{false}">
>    <ui:include src="myPage.xhtml" />
> </seam:fragment>
> normally nothing should be initialized related with myPage.xhtml bu all beans are initialized. In seam 2.2.2.Final this works as expected
> simple workaround is use <c:if> instead of <seam:fragment>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira