[
https://issues.jboss.org/browse/CDI-377?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger commented on CDI-377:
-------------------------------------
This is not how Java EE works. You have to retain backwards compatibility. You can define
what was previously optional or undefined (e.g. implicit bean archive support in CDI 1.0)
but you cannot change defined behavior.
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