[cdi-dev] [JBoss JIRA] (CDI-377) automatic JSR-330 annotation processing problematic

[Antoine Sabot-Durand (JIRA)]

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

Antoine Sabot-Durand commented on CDI-377:
------------------------------------------

Romain, I don't understand the need for another descriptor. Providing this exclusion mechanism in beans.xml seems portable on Java EE and SE. Reuben proposal to provide an <exclude jar/> with a lis or a pattern seems the simpler choice.

Now we could also decide to provide a bean-discovery mode in which we do not to allocate beans in beans archives if the application doesn't define injection points with classes from these bean archive (if you don't use these classes as beans sot they're not beans). This solution would be more elegant IMO and simpler for devs.
                
> automatic JSR-330 annotation processing problematic
> ---------------------------------------------------
>
>                 Key: CDI-377
>                 URL: https://issues.jboss.org/browse/CDI-377
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Java EE integration
>    Affects Versions: 1.1.PFD
>         Environment: glassfish-4
>            Reporter: Reuben Pasquini
>              Labels: CDI, guava, guice
>             Fix For: 1.1.PFD
>
>
> The jsr-330 dependency injection annotations (javax.inject.*) find use in javase environments using IOC packages like guice.
> Adding a dependency on a jar that uses guice or whatever in a javase environment
> to a war deployed to a jee7 container 
> results in CDI processing annotated classes intended for 
> app-managed injection.  See this ticket filed with guava for a concrete example:
>     https://code.google.com/p/guava-libraries/issues/detail?id=1433

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira