[
https://issues.jboss.org/browse/CDI-377?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-377:
-----------------------------------
and to be even more specific: 2.5 defines 'Any scope type is a bean defining
annotation'. This means also JSR-330 @Scopes will trigger this.
The other part which might cause this issue is the Extension scanning. Because in CDI-1.1
this will not only get fired for all those beans with bean defining annotation but for all
classes in all JARs, right?
It would have been helpful if Weld would catch those ClassNotFound and NoClassFoundDef
stuff and log the Bean which currently gets processed. That way we would have better info
about what really happens.
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