[
https://issues.jboss.org/browse/JBSEAM-5050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Murat HAZER updated JBSEAM-5050:
--------------------------------
Description:
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>
was:
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
> 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
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
