<div dir="ltr">Hi all,<div><br></div><div>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. </div><div><br></div><div>CDI Spec:</div><div><span style="color:rgba(0,0,0,0.8);font-family:'Noto Serif','DejaVu Serif',serif;font-size:17px;letter-spacing:-0.17px;line-height:27.2px">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 type</span><code style="font-family:'Droid Sans Mono','DejaVu Sans Mono',monospace;font-size:0.9375em;color:rgba(0,0,0,0.901961);letter-spacing:0px;padding:0.1em 0.5ex;word-spacing:-0.15em;border-radius:4px;line-height:1.45;background-color:rgb(247,247,248)">javax.enterprise.context.BusyConversationException</code><span style="color:rgba(0,0,0,0.8);font-family:'Noto Serif','DejaVu Serif',serif;font-size:17px;letter-spacing:-0.17px;line-height:27.2px">.</span><br></div><div><br></div><div><br></div><div>It would be helpful if a common configurable concurrency mechanism (EJB Singleton style locking?) could be established for all normal scopes. </div><div><br></div><div>What are your thoughts on this?</div><div><br></div><div>Regards,</div><div><br></div><div>Stephan</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div><div><br></div><div><br></div><div><div><div class="gmail_signature"><br>______________________________________<br><b>Stephan Knitelius</b><br>Alteburger Str. 274<br>50968 Köln / Cologne<br>Deutschland / Germany<br><a href="mailto:stephan@knitelius.com" target="_blank">stephan@knitelius.com</a></div></div>
</div></div>