[
https://issues.jboss.org/browse/CDI-18?page=com.atlassian.jira.plugin.sys...
]
Ales Justin commented on CDI-18:
--------------------------------
> @Ales: In fact, JBossAS7 already killed the BDA partly! You
already contradict the spec by allowing definitions in WEB-INF/beans.xml to count for all
jars in WEB-INF/lib. Please go back and read the spec - this is clearly defined different!
As per the CDI-1.0 spec, any definitions in WEB-INF/beans.xml must ONLY affect
WEB-INF/classes/** and MUST NOT have any effect on jars in WEB-INF/lib!
I don't think that's true for AS7. Are you 100% sure?
It was true for AS6, but that was a mistake / bug.
And what do you mean by "affect"?
Global enablement of interceptors, decorators and alternatives
--------------------------------------------------------------
Key: CDI-18
URL:
https://issues.jboss.org/browse/CDI-18
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Beans, Decorators, Interceptors, Packaging and Deployment
Affects Versions: 1.0
Reporter: Mark Struberg
Priority: Critical
Fix For: 1.1 (Proposed)
Currently the spec defines that <interceptors>, <decorators> and
<alternatives> affect only the Bean Archives where they are configured in (via
beans.xml).
Thus if you e.g. enable an Alternative in a WEB-INF/beans.xml, it does NOT count for the
jars in it's WEB-INF/lib folder!
This is pretty unhandy because you would need to repackage all your jars in your
WEB-INF/lib folder and add/expand the <alternatives> sections in their beans.xml.
Needless to say that this is not only hard to do in a company build but is also
impossibly to handle at deploy time in an OSGi environment!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira