[
https://issues.jboss.org/browse/CDI-377?page=com.atlassian.jira.plugin.sy...
]
Antoine Sabot-Durand commented on CDI-377:
------------------------------------------
[~jharting] I understand what you're saying but I don't agree. That's what
I'd call a general guidelines, but when we decided something wrong (a mistake that we
didn't foreseen) we have to do something.
And we already broke this rule by reverting things in CDI-389. We have the opportunity to
correct an issue before mainstream developer start seriously using CDI 1.1+.
Sorry to say that but there are zillions of Spring and Guice libs out there with dev team
that don't care about CDI and that will have no reason or interest to add a beans.xml
file to their lib.
This critical ticket is 9 months old with no satisfying solution. At this step I think
nobody can comme in the discussion and simply say "no" without a constructive
solution. So what do you suggest to fix this?
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