[
https://issues.jboss.org/browse/CDI-659?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-659:
----------------------------------
Sure, why not. I'm all for any ideas that will make CDI/Servlet integration easier. By
the way, the other thing missing is dependency injection into servlet components
(servlers, listeners, etc.). Right now, there is no Servlet SPI which would allow the CDI
container to hook into the component lifecycle and Servlet impls are not required to
perform injection (I'm not sure about Servlet 4.0). And so CDI impls must depend on
non-portable (often very unstable) SPIs. CDI-492 is also related.
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)