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

[Marius Bogoevici (JIRA)]

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

Marius Bogoevici commented on JBAS-8683:
----------------------------------------


    OK, container == BeanManager, but still: 

- extensions are clearly defined as application-scoped, which means that there must be only one extension instance per deployment (not per BM/webapp).
 - even if the above is true, I agree that it is possible to apply a scoping mechanism so that "only extensions that are visible to a given BM can receive events that are applicable to that BM", but while this mechanism is reasonable, I don't think that this is what the released spec requires us to do and it's also ambiguous, without further clarification.

But apart from this discussion - the practical limitation to this is the current Weld approach, which simply does not support per-module extensions. So I'll leave to Pete to confirm whether he thinks that the current spec really does require us to do so and consequently whether or when this will be supported.



> CDI Extensions not discovered in EAR structure
> ----------------------------------------------
>
>                 Key: JBAS-8683
>                 URL: https://jira.jboss.org/browse/JBAS-8683
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Weld/CDI
>            Reporter: Heiko Braun
>            Assignee: Marius Bogoevici
>            Priority: Optional
>             Fix For: TBD
>
>
> 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