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

Mark Struberg (Commented) (JIRA) jira-events at lists.jboss.org
Thu Dec 8 09:09:40 EST 2011

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

Mark Struberg commented on CDI-18:

Ales, fact is that lots of applications I know which must get deployed to Glassfish or JBossAS6 (not sure yet about AS7) currently just *unpack* all their dependencies to WEB-INF/classes, BECAUSE BDA IS COMPLETELY FUUUU UP....

Have you ever worked with big customers to get their _big_ CDI apps working? I did, and trust me, BDA is really a nightmare!

This is really the worst part of CDI-1.0, and it's _very_ easy to get rid of it!

Just look at what seam-solder does with @DefaultBean to make parts of this undone with some dirty tricks...
@DefaultBean disables the BDA by emulating other mechanism - but at a pretty high performance and complexity cost.
And then look at how many parts of Seam are using @DefaultBean? 80%? 90%? Even more? 

> 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


More information about the cdi-dev mailing list