[seam-issues] [JBoss JIRA] (JBSEAM-4898) JSF2 Page Scope components are not active on postback

[John Gilbert (JIRA)]

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

John Gilbert commented on JBSEAM-4898:
--------------------------------------

I have attached 2 sample apps. The jsf2 profile builds the app with seam 2.3 and the jsf1 profile builds the app with seam 2.2. Build the jsf2 profile first and then deploy both apps at the same time. I am using AS 5.1. The apps have links to each other so you can switch back and forth. The page and conversation scopes are not working in 2.3.

This is a sample of the facelets the retrieve the template and include view id from scoped factories.

{code}
<ui:composition xmlns="http://www.w3.org/1999/xhtml"
	xmlns:ui="http://java.sun.com/jsf/facelets"

	template="#{pageScopedTemplate}">

	<ui:define name="body">
		<ui:include src="#{pageScopedInclude}" />
	</ui:define>

</ui:composition>
{code}

Also, the ear build is current configured for expanded mode.

                
> JSF2 Page Scope components are not active on postback
> -----------------------------------------------------
>
>                 Key: JBSEAM-4898
>                 URL: https://issues.jboss.org/browse/JBSEAM-4898
>             Project: Seam 2
>          Issue Type: Bug
>            Reporter: John Gilbert
>         Attachments: seam-scope-test-master.zip
>
>
> Page scoped components are not active on postback during the restore view phase. We have been doing things like this in JSF 1.2 for years with no trouble.
> {code}
> <ui:include src="#{pageScopedComponent.viewId}" />
> {code}
> In JSF 2 the page will render, because the facelet isn't actually complied until the render phase on a GET. Then on postback the component is not found in the stateful page scope and then isn't created because the page scope is not active yet.
> I have made many attempts to debug this but I have run out of ideas. I'm thinking this is a bug so I am posting it here. But if someone can give me some fresh ideas on where to look, I will keep digging.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira