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

[ https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-129: ------------------------------- Bill Shannon points out that we also need to consider visibility of the bean when clarifying this. For example, if you have the same bean class specified in two separate wars, both of which are application scoped, you can't share the state between the two (as you would get a CCE). In fact, this makes me wonder if there isn't an "obvious" solution staring us in the face? If we clarify that @ApplicationScoped means "shared across the ear" and also that the same bean class packaged in two locations which are not visible to one another (e.g. warA and war B) and cannot share state. Now we provide both options of ear scoped state and war scoped state, and the state is only shared if the bean class is packaged in a shared library or shared module (e.g. ejb module). This seems like a good solution: a) it means we don't need to proliferate the number of "application scoped" annotations b) it makes logical sense (if a user wants per-war state, package the bean in a war, if the user wants shared-ear state, then package it as a shared lib). WDYT? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira