[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:22:26 EDT 2011

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

Mark Struberg commented on CDI-142:

Not really. If you would define that @ApplicationScoped beans are 1 instance for all webapps, then of course no @Specializes sitting in a WAR WEB-INF/classes would be possible. Because this specialisation implementation (class visibility) is only available from that very webapp. I just have no idea how we could spec that in a way which would be implementable without breaking other specs (namely the EE spec).

> 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