[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
Mon Sep 19 07:02:26 EDT 2011

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

Mark Struberg commented on CDI-142:

2 side notes:

a.) Imo 'across bean archives boundaries' is not the real problem but 'across class visibility boundaries' is.
 One can argue that this means the same, but 2 JAR files in the same WEB-INF/lib of webapp1 cause absolutely no problems. Those problems only arise if we hit class visibility boundaries imo.

b.) This not only hits @Specializes but also @Alternative, interceptors, decorators, etc

> 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