[
https://issues.jboss.org/browse/CDI-18?page=com.atlassian.jira.plugin.sys...
]
Mark Struberg reopened CDI-18:
------------------------------
sorry, the wording of 5.1.1 is out of any concept.
This didn't get easier but is now almost impossible to implement!
Things like
{quote}
An alternative selected for an application may be deselected for a bean archive using the
<alternatives> element of the beans.xml file of the bean archive. The
<alternatives> element contains a list of bean classes and stereotypes, along with a
disabled flag. An alternative is not selected for the bean archive if either..
{quote}
That complicates the useless and utter broken rules of CDI-1.0 even more. Please let's
just get rid of those BDA implications and focus on solving the modularity properly.
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
Assignee: Pete Muir
Priority: Critical
Fix For: 1.1.PRD
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
For more information on JIRA, see:
http://www.atlassian.com/software/jira