[
https://issues.jboss.org/browse/CDI-142?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-142:
-----------------------------------
here is an example of such a problematic scenario
* EAR with webapp1 and webapp2
* EAR contains @ApplicationScoped MailService (in a shared ejb-jar)
* webapp2 contains @Specializes MyOtherMailService extends MailService
* we have proper ClassLoader isolation between webapp1 and webapp2
now we use @Inject MailService in webapp1 and webapp2,
* what do they get?
* what if we shutdown webapp2 programmatically?
No impl specifics around here, just pure specc issues imo...
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