<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">We've discussed this issue before. I
definitely still think @Lock belongs in a modular CDI
specification. It would be highly useful to both @Singleton and
@ApplicationScoped. Today if I need to use declarative concurrency
control for a shared component I am essentially forced to use EJB
singleton - which shouldn't be the case and perhaps should not
have been the case past Java EE 6.<br>
<br>
On 2/19/2016 5:27 AM, Stephan Knitelius wrote:<br>
</div>
<blockquote
cite="mid:CAGMB8Y2jyse-H66Ty3fw9bhS31h_2eXtQ9Sv=9cMSrXbyY_fGw@mail.gmail.com"
type="cite">
<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 moz-do-not-send="true"
href="mailto:stephan@knitelius.com" target="_blank">stephan@knitelius.com</a></div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
cdi-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/cdi-dev">https://lists.jboss.org/mailman/listinfo/cdi-dev</a>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a class="moz-txt-link-freetext" href="http://www.apache.org/licenses/LICENSE-2.0.html">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.</pre>
</blockquote>
<br>
</body>
</html>