[
https://issues.jboss.org/browse/CDI-377?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba updated CDI-377:
-----------------------------
Comment: was deleted
(was: [~struberg] it's not entirely a hack but rather an example how to leverage the
spec requirement, see also 12.1 Bean archives:
{quote}
"For compatibility with Contexts and Dependency 1.0, products must contain an option
to cause an archive to be ignored by the container when no beans.xml is present."
{quote}
But I agree the field should not be vendor-specific.)
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