[
https://issues.jboss.org/browse/CDI-188?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-188:
-----------------------------------
Let's start at the beginning:
a.) where is this defined in the CDI spec? Imo there is no such a wording!
b.) the only restriction is that getBeans by name must resolve to one unique Bean
otherwise an AmbiguousResolutionException gets thrown. (section 11.3.7)
But according to the EE spec, WebAppA must not see Classes (and thus Beans) from WebAppB.
I expect you are using an EE server with a flat out isolation, or Weld simply ignores the
isolation. But that's not a problem in the spec itself imo.
Pete, do you agree?
Bean in different wars should be allowed to have the same EL name
-----------------------------------------------------------------
Key: CDI-188
URL:
https://issues.jboss.org/browse/CDI-188
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Stuart Douglas
Fix For: 1.1 (Proposed)
Normally two beans with the same @Named would be treated as an error. If they are in
sperate war's this should be allowed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira