[cdi-dev] [JBoss JIRA] Issue Comment Edited: (CDI-129) Clarify behaviour of @ApplicationScoped in EARs

[ https://issues.jboss.org/browse/CDI-129?page=com.atlassian.jira.plugin.sy... ] Stuart Douglas edited comment on CDI-129 at 5/18/11 7:41 AM: ------------------------------------------------------------- (Opps, when I opened this the history tab was open rather than comments, and I did not realise that this had already been said) The Final Release of JSR-299 does not define anything to do with @ApplicationScoped in 6.5.2. @ApplicationScoped is defined in 6.7.3 and states: "The application context is shared between all servlet requests, web service invocations, EJB remote method invocations, EJB asynchronous method invocations, EJB timeouts and message deliveries to message-driven beans that execute within the same application. The application context is destroyed when the application is shut down." This means that @ApplicationScoped is shared over a whole ear, and is not per war (there may not even be a war in the ear). was (Author: swd847): The Final Release of JSR-299 does not define anything to do with @ApplicationScoped in 6.5.2. @ApplicationScoped is defined in 6.7.3 and states: "The application context is shared between all servlet requests, web service invocations, EJB remote method invocations, EJB asynchronous method invocations, EJB timeouts and message deliveries to message-driven beans that execute within the same application. The application context is destroyed when the application is shut down." This means that @ApplicationScoped is shared over a whole ear, and is not per war (there may not even be a war in the ear). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira