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

[Ales Justin (Issue Comment Edited) (JIRA)]

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

Ales Justin edited comment on CDI-18 at 12/8/11 9:26 AM:
---------------------------------------------------------

I'm not saying BDA impls are perfect :-), but I do think we need some abstraction like BDA.
It's easy to say we don't need it, and let's then make everything flat.
Which is - as you say - probably how big JEE apps look like, but not everything is JEE. ;-)
e.g. we had a big customer with MicroContainer (AS5/6 kernel), which used custom CL rules, 
and having BDA would make it possible for them to use CDI, if they wanted (this was pre-CDI).

btw: how do you then follow bean visibility rules in OWB in hierarchy .ears?

                
      was (Author: alesj):
    I'm not saying BDA impls are perfect :-), but I do think we need some abstraction like BDA.
It's easy to say we don't need it, and let's then make everything flat.
Which is - as you say - probably how big JEE apps look like, but not everything is JEE. ;-)
e.g. we had a big customer with MicroContainer (AS5/5 kernel), which used custom CL rules, 
and having BDA would make it possible for them to use CDI, if they wanted (this was pre-CDI).

btw: how do you then follow bean visibility rules in OWB in hierarchy .ears?

                  
> 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