[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2263) Page-scoped components not accessible in jPDL page initial actions

Pete Muir (JIRA) jira-events at lists.jboss.org
Tue Mar 11 08:20:58 EDT 2008

     [ http://jira.jboss.com/jira/browse/JBSEAM-2263?page=all ]

Pete Muir updated JBSEAM-2263:

    Fix Version/s: 2.1.x

> Page-scoped components not accessible in jPDL page initial actions
> ------------------------------------------------------------------
>                 Key: JBSEAM-2263
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2263
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: BPM
>    Affects Versions: 2.0.0.GA
>            Reporter: Matthew Lieder
>             Fix For: 2.1.x
> See the following page declaration (selectEmployeePageBean is scoped to the page):
> <page name="selectEmployee" view-id="/selectEmployee.xhtml">
> 	<action expression="#{selectEmployeePageBean.setShowDetails(true)}" />
> 	<transition to="somewhere" />
> </page>
> The problem is that when selectEmployee.xhtml is being rendered, selectEmployeePageBean.showDetails is false -- the bean is actually created twice, once for the action expression and again when accessed from the page renderer, and thus loses its state. I would think that the page scope should begin before the action expressions for that page are evaluated. That would allow me to easily customize pages from the pageflow definition (useful if in some places I want a "Next" button instead of "Finish", or want details to be shown in only one place, etc.) without having to make page-specific beans conversation-scoped.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list