[ https://issues.jboss.org/browse/JBSEAM-5050?page=com.atlassian.jira.plugi... ] 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 -- 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

[ https://issues.jboss.org/browse/JBSEAM-5050?page=com.atlassian.jira.plugi... ] 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... 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. -- 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