[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1959) Wildcard page view-id (*) in pages.xml file with login-required="true" cause error.
[ http://jira.jboss.com/jira/browse/JBSEAM-1959?page=comments#action_12379640 ]
Pete Muir commented on JBSEAM-1959:
-----------------------------------
Problem is with ResourceLifecycle.send(). If Seam does a redirect in
FacesManager.redirect, it calls facesContext.responseComplete(); in JSF this causes
further phases to not be executed. ResourceLifecycle.send() doesn't do this.
As Seam has sent a redirect (and set responseComplete), the SeamPhaseListener listener
assumes it's at the end of the request so tears down the contexts etc. further phases
are executed and so seam contexts aren't available.
Wildcard page view-id (*) in pages.xml file with
login-required="true" cause error.
-----------------------------------------------------------------------------------
Key: JBSEAM-1959
URL: http://jira.jboss.com/jira/browse/JBSEAM-1959
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.0.CR1
Environment: Windows XP Pro SP2
JBoss AS 4.2.0.GA
JBoss Seam 2.0.0.CR1
Reporter: Francisco Antônio
Assigned To: Pete Muir
Fix For: 2.0.0.CR2
The use of <page view-id="*" login-required="true" > in
pages.xml file causes the following errors:
a) ERROR [ResourceLifecycle] Exception in PhaseListener, render view : beforePhase
java.lang.IllegalStateException: No active application scope
and
b) ERROR [ResourceLifecycle] Exception in PhaseListener, render view : beforePhase
java.lang.IllegalStateException: No application context active
If login-required="true" is just removed the above errors disappear.
--
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