[cdi-dev] [JBoss JIRA] (CDI-239) Define Extension notification rules for shared libraries

[Pete Muir (JIRA)]

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

Pete Muir commented on CDI-239:
-------------------------------

We would propose that an extension should only get fired if the *class* can see the *extension* (which is perhaps the inverse of what you might expect).
                
> Define Extension notification rules for shared libraries
> --------------------------------------------------------
>
>                 Key: CDI-239
>                 URL: https://issues.jboss.org/browse/CDI-239
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Portable Extensions
>    Affects Versions: 1.1.EDR
>            Reporter: Mark Struberg
>             Fix For: 1.1 (Proposed)
>
>
> Consider an EAR file with a shared xy.JAR file in the EARs ./lib folder with an
> @EnterpriseApplicationScoped class X 
> and a 
> @RequestScoped class Y
> The EAR also contains 2 web applications WebAppA and WebAppB.
> WebAppA has ExtensionA in it's WEB-INF/classes and WebAppB has ExtensionB in it's classes both with a public void met(@Observes ProcessAnnotatedType pat) and each modifying the AnnotatedType.
> What should happen here? Will there be 2 Bean<T> for X and 2 for Y? (one Bean for each WebApp)? or will X and Y not trigger a ProcessAnnotatedType for the extensions defined in the webapps (but only for Extensions defined in the shared ear lib)?

--
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