[cdi-dev] [JBoss JIRA] (CDI-18) Global enablement of interceptors, decorators and alternatives

[Mark Struberg (JIRA)]

    [ https://issues.jboss.org/browse/CDI-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737010#comment-12737010 ] 

Mark Struberg commented on CDI-18:
----------------------------------

There are quite some options. E.g. disabling BDA if a single beans.xml with version="1.1" gets detected. This got used in JPA, JSF, etc. So really nothing to worry about.

Btw, even lots of JBoss folks actively involved in real world projects have acknowledged that BDA is utter broken. See the discussion and solution attempt around JBoss Solder DefaultBean...

Add to that that only a minority EE container currently implements the strict BDA rules which got defined in CDI-1.0. Quite some of them treat all WEB-INF/lib/*.jar + the WEB-INF/classes as a single BDA it seems. JBossAS7 is amongst them as far as a small sample application showed.
                
> 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