-
Feature Request
-
Resolution: Obsolete
-
Major
-
None
-
2.0-EDR1
-
None
Currently the spec only defines, a non-configurable, concurrency control mechanism for conversation scope. All other build-in scopes remain unprotected, relaying on the developer.
It would be useful to introduce EJB Singleton style concurrency control for CDI scopes.
Allowing the developer to configure the concurrency behavior of ConversationScoped beans, and defining concurrency control for the other build-in scopes.
[CDI-582] Configurable concurrency control for CDI
Martin Kouba
added a comment - http://lists.jboss.org/pipermail/cdi-dev/2016-February/007769.html 
Reza Rahman (Inactive)
added a comment - I think this is very important and way past due to further broaden CDI adoption. I'd say this class of CDI features is probably more important than what is currently slated for CDI 2 (which I seriously fear will be basically ignored as low-level stuff not relevant to most real world potential and current CDI users).
Reza Rahman (Inactive)
added a comment - I think this is very important and way past due to further broaden CDI adoption. I'd say this class of CDI features is probably more important than what is currently slated for CDI 2 (which I seriously fear will be basically ignored as low-level stuff not relevant to most real world potential and current CDI users). 
The CDI project is part ofJakarta and uses GitHub issues as it's issue tracking system.
Therefore, all issues in CDI JIRA project are being bulk-closed as described in this GitHub issue.
If you feel like this particular issue deserves ongoing discussion, investigation or fixes in CDI/CDI TCK, please create a new issue under GitHub repository and include a link to this JIRA.
For specification related question/issues, please use - https://github.com/eclipse-ee4j/cdi/issues
For CDI TCK related questions/issues, please use - https://github.com/eclipse-ee4j/cdi-tck/issues