[
https://issues.jboss.org/browse/CDI-152?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-152:
--------------------------
Fix Version/s: TBD
(was: 1.1 (Proposed))
Affects Version/s: 1.0
Deferring, as Java EE does not specify at all the order in which individual components
start up, and doesn't plan to, which makes this very hard to specify.
Access the web.xml from CDI extensions
--------------------------------------
Key: CDI-152
URL:
https://issues.jboss.org/browse/CDI-152
Project: CDI Specification Issues
Issue Type: Feature Request
Affects Versions: 1.0
Reporter: Brian Leathem
Fix For: TBD
Currently it is not possible to access the web.xml file from CDI extensions in a portable
way, since the ServletContext is not available from CDI extensions (at least in EE
enviroments).
I filed a Servlet spec issue to make the web.xml file accessible, prior to the the
ServletContext being initialized:
http://java.net/jira/browse/SERVLET_SPEC-9
Perhaps as an alternative solution, CDI could do something to delay CDI extensions from
loading until the ServletContext is available? Since this is the case for Servlet
environments, would it not be acceptable for EE environments as well?
--
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