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

[Jozef Hartinger (JIRA)]

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

Jozef Hartinger commented on CDI-377:
-------------------------------------

{quote}1. no-beans.xml wouldn't work since when you dev for a servlet container you don't care then when you are deployd in a EE containet you don't want to repackage.{quote}
Right, this would be helpful only if the library authors care. This may not be the entire solution of the problem but may be part of it. The important point here is that even if we get rid of @Singleton support, there would still be no portable way (across CDI 1.0, 1.1 and 1.2) of saying that this archive with CDI scopes is not intended to be a bean archive (i.e. bean-discovery-mode="none").

{quote}2. would mean you can't write cdi code with @Singleton (so excluding it would be better) and makes understanding of issues harder{quote}
You can write CDI code in @Singletons as long as your archive also has something else than singletons in it. Agreed that this is more complicated than just getting rid of @Singleton. On the other hand, all CDI implementations are also supposed to implement CDI-330 so I am no sure if we can just get rid of it.

{quote}Maybe we could veto a module (abstraction for jar, classes dir ...) before scanning it?{quote}
To me this sounds way out of scope for a maintenance release.
                
> 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_spec_chge, CDI_tck_chge
>             Fix For: 1.2 Proposed
>
>
> 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