[cdi-dev] [JBoss JIRA] Commented: (CDI-142) Clarify behaviour of specializing beans across bean archive boundaries

Mark Struberg (JIRA) jira-events at lists.jboss.org
Sun Sep 18 13:39:26 EDT 2011

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

Mark Struberg commented on CDI-142:

Even if you have 1 BeanManager for the whole EAR doesn't change anything that you cannot have both behaviours at a time! At least not with a proper classpath isolation which is recommended by the EE spec. 
a) make war local classes @Specializes @AppicationScoped beans from a shared ear-lib, or
b) have @ApplicationScoped being 1 per EAR. 

both at the same time would require that no class isolation exists - and I hope we are d'accord that this is not anything we would suggest and even more - not make it a required behaviour ;)

> Clarify behaviour of specializing beans across bean archive boundaries
> ----------------------------------------------------------------------
>                 Key: CDI-142
>                 URL: https://issues.jboss.org/browse/CDI-142
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Beans, Resolution
>    Affects Versions: 1.0
>            Reporter: Stuart Douglas
>             Fix For: 1.1 (Proposed)
> For instance, if a bean in a war specializes a bean in an ejb jar does the bean in the war become visible to other bean archives that would not normally be able to see it?

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


More information about the cdi-dev mailing list