[
https://issues.jboss.org/browse/CDI-377?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-377:
-----------------------------------
Jozef, I suggest to not use the Workaround fields of the CDI tracker to point to
workarounds which are _not_ in the spec but a vendor specific hack.
It might be better to create a respective WELD or JBOSSAS/ WILDFLY issue where you add the
workaround howto and we link over to this issue from here.
The workaround fix in CDI should only be used for workarounds which are valid within the
spec or work on all servers by a common JavaEE feature.
E.g. for BDA @Alternative (CDI-18) most of the time one can use @Specializes which
(funnily) do not respect BDA restrictions. That would be fine to mark as workaround in the
very CDI issue.
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