[cdi-dev] [JBoss JIRA] Commented: (CDI-129) introduce @EnterpriseScoped (or similar)

[ https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-129: ----------------------------------- Probably because of the heavily underspecified classloader behaviour in EE in this area? I was really confused about this too also. Because the Servlet spec (which the EE umbrella spec references prominently) imo _exactly_ defines that WebApplications must not interfere with other WebApplications but must be isolated well from each other. But most old EE servers (JBoss4 and 5 are perfect examples for this, as are the old WebLogics) ship with almost no isolation at all it seems! I actually never understood why they behave this way as _default_! @Marius: A Bean can only be used in a shared library if it's type is available on the shared classpath too. E.g. in a ejb-jars lib. And even if one webapp uses an @Alternative which is only available in this very one webapp, then there is no problem. Because injecting an @ApplicationScoped bean will still give you the contextual reference (the proxy). They simply refer to different contextual instances. There is really not much difference to a @SessionScoped bean of which it's class is in a shared ejb-jars lib. Or am I overlooking something? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira