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

[Reuben Pasquini (JIRA)]

     [ https://issues.jboss.org/browse/CDI-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reuben Pasquini resolved CDI-377.
---------------------------------

    Fix Version/s: 1.1.PFD
       Resolution: Done


I just discovered the "bean-discovery-mode" attribute for beans.xml - which is just what I needed to prevent CDI from scanning a jar.  
    https://code.google.com/p/guava-libraries/issues/detail?id=1433#c17

Problem solved - sorry for the bad bug report ...

                
> 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