Hi all,
CDI spec does not define a common concurrency control mechanism. The time any type of concurrency control is mentioned is in conjunction with EJB and a rather restrictive one for conversation context.
CDI Spec:
The container ensures that a long-running conversation may be associated with at most one request at a time, by blocking or rejecting concurrent requests. If the container rejects a request, it must associate the request with a new transient conversation and throw an exception of typejavax.enterprise.context.BusyConversationException.
It would be helpful if a common configurable concurrency mechanism (EJB Singleton style locking?) could be established for all normal scopes.
What are your thoughts on this?
Regards,
Stephan
______________________________________
Stephan KniteliusAlteburger Str. 274
50968 Köln / Cologne
Deutschland / Germany
stephan@knitelius.com