[jboss-jira] [JBoss JIRA] Commented: (JBAS-8683) CDI Extensions not discovered in EAR structure

[Mark Struberg (JIRA)]

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

Mark Struberg commented on JBAS-8683:
-------------------------------------

oops, almost forgot about this already. I'm seriously unhappy about the @ApplicationScoped bean definition as being @EarScoped.

Reason is that a bean which got created as @Alternative in a WebApp classloader will not be available to the MDB as of in your example. Mixing up those classloader hierarchy junks will give you the same bloody result as the current EE ClassLoader specification: THERE IS NO SUCH THING! There is no ClassLoader spec for EE, so we should go with the only safe bet: application == web application! 

E.g. webapp1 -> 1 instance; webapp2 -> 1 instance; MDBs, Quartzed tasks (all which gets loaded via the Ears standard classloader) -> 1 instance.

If we don't clearly define this in the CDI spec, then the portability would be gone because this would work different in EVERY EE server.


> CDI Extensions not discovered in EAR structure
> ----------------------------------------------
>
>                 Key: JBAS-8683
>                 URL: https://issues.jboss.org/browse/JBAS-8683
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Weld/CDI
>    Affects Versions: 6.0.0.Final
>            Reporter: Heiko Braun
>            Assignee: Marius Bogoevici
>            Priority: Critical
>             Fix For: 6.1.0
>
>
> A web application contains a CDI extension shipped within WEB-INF/lib. If this web application is packaged in an EAR, the extension will not be discovered and executed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira