[
https://issues.jboss.org/browse/CDI-18?page=com.atlassian.jira.plugin.sys...
]
Mark Struberg commented on CDI-18:
----------------------------------
RE: The <first> <others> turned out to be not flexible
enough for lots of situations. Thus I prefer
an ordinal with a float value. Hmmm.. Ok.
My comment was targeted at the mechanism used in the faces-config.xml which I assume has
the same mechanism (need to re-read the servlet 3.0 spec though). Problem there is that
the ordering is for the whole config file, isn't? So you could only define the order
of all the stuff in the beans.xml. Not sure if we need that, but in case of the
faces-config.xml I definitely regretted it already: I did want to have the EL-order in a
different way than the facelets resource order which doesn't work.
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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira