[cdi-dev] [JBoss JIRA] (CDI-659) Introduce a provider in-specific servlet listener

Romain Manni-Bucau (JIRA) issues at jboss.org
Mon Dec 5 08:52:00 EST 2016

    [ https://issues.jboss.org/browse/CDI-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13333892#comment-13333892 ] 

Romain Manni-Bucau commented on CDI-659:

+1 for ServletContainerInitializer, would it makes sense to have a scanning mode relying on this as well and avoiding CDI to scan anything (@HandleTypes)?

> 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

More information about the cdi-dev mailing list