[
https://jira.jboss.org/jira/browse/WELD-29?page=com.atlassian.jira.plugin...
]
David Allen commented on WELD-29:
---------------------------------
The exception mentioned in the forum is no longer thrown when the error page is rendered,
but there remain a few problems with contexts during error page processing:
1) With the JSF 2 RI, there is no FacesContext available and thus the page cannot really
use JSF.
2) There is no CDI context other than the conversation context during processing of this
page. This is mostly due to the way Servlet listeners are handled for the error page. No
listeners are invoked around the error page processing.
If JSF is used in the error page, an exception will be thrown that no FacesContext exists.
Only CDI beans from the conversation scope are available to the EL resolver.
web.xml configured jsf error-page throws ContextNotActiveException
------------------------------------------------------------------
Key: WELD-29
URL:
https://jira.jboss.org/jira/browse/WELD-29
Project: Weld
Issue Type: Bug
Components: GlassFish Integration, Scopes & Contexts, Web Tier integration
(JSF, JSP, EL and Servlet)
Affects Versions: 1.0.0.PREVIEW1
Environment: glassfish V3 prelude, jsf 2.0.0-SNAPSHOT (May 17 2009)
Reporter: Guy Veraghtert
Assignee: David Allen
Fix For: 1.0.1.CR1
An ContextNotActiveException is thrown by Web beans when the container tries to forward
to a jsf error-page (configured in web.xml). See forum reference.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira