[
https://issues.jboss.org/browse/CDI-659?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-659:
----------------------------------
Tomas is right. We would have to specify the Servlet container support first as there are
other problems we would have to deal with (e.g. read-only JNDI). By the way, an impl. may
leverage {{javax.servlet.ServletContainerInitializer}} API to initialize the CDI container
(this should work on most recent versions of Tomcat, Jetty, etc.).
Introduce a provider in-specific servlet listener
-------------------------------------------------
Key: CDI-659
URL:
https://issues.jboss.org/browse/CDI-659
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Java EE integration
Reporter: John Ament
Fix For: 2.1 (Discussion)
Currently, each provider (OWB, Weld) provides a servlet listener for registering CDI in a
plain servlet container. Looking at other specs, e.g. JAX-RS, references to an
implementation in-specific way to register your services are provided. We should do the
same for CDI, allowing a user to register a servlet listener without needing to leverage
provider-specific classes.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)