[cdi-dev] [JBoss JIRA] Commented: (CDI-142) Clarify behaviour of specializing beans across bean archive boundaries
[
https://issues.jboss.org/browse/CDI-142?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-142:
-----------------------------------
We had this discussion in another issue where we discussed about @ApplicationScoped vs
@EarScoped (which does not yet exist) in CDI-129. We could make our live easy if we say
that @ApplicationScoped (which is the vast majority of beans) is _per_ _webapp_ (+ one for
the 'shared' stuff like JMS), because every WebApp has it's own BeanManager
anyway.
Then we can go on and say that 'an @EarScoped bean must only be specialized,
alternated, etc in a library which is accessible to all @ApplicationScoped beans'.
Which means a shared ejb-jar lib in a EAR.
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
Reporter: Stuart Douglas
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