[cdi-dev] [JBoss JIRA] (CDI-377) automatic JSR-330 annotation processing problematic
[
https://issues.jboss.org/browse/CDI-377?page=com.atlassian.jira.plugin.sy...
]
Romain Manni-Bucau commented on CDI-377:
----------------------------------------
Well this issue is general to JavaEE. typically using spring you'll likely use
@PersistenceContext, @Resource etc... and the JavaEE container can scan it (since it scans
the whole app) and then try to do something and fail. In TomEE we solve it allowing to
configure a list of excluding jars (a bit like Reuben said) but the issue would be to make
it a CDI config since that's a JavaEE issue. Typically being able to *exclude*
complete jars (surely from a pattern) would be awesome but needs IMO another descriptor
usable in SE and EE mode.
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