[
https://issues.jboss.org/browse/CDI-379?page=com.atlassian.jira.plugin.sy...
]
Jens Schumann commented on CDI-379:
-----------------------------------
As stated in CDI-370 I still believe the CDI spec is way to verbose regarding scopes and
related APIs. I think it would be better to move most of the stuff to the related specs
(servlet, ejb, ...) or even the Java EE umbrella. Same applies to CDI-380.
Clarify life cycle of RequestScoped
-----------------------------------
Key: CDI-379
URL:
https://issues.jboss.org/browse/CDI-379
Project: CDI Specification Issues
Issue Type: Clarification
Reporter: Joseph Snyder
Priority: Minor
This is one of the areas where the CDI spec could be clearer. It defines
the points where "some" request scope is active, and where "some"
request
scope is destroyed, but it doesn't clearly state what the span of a particular
request context is. You sort of have to work backwards and figure it out.
Update the spec to indicate when a particular request scope is
created, what operations it's active during, and when it's destroyed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira