<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Antonio,<br>
<br>
I saw one thread about moving Servlet related scopes to servlet
spec (I agree with that step!), but there was no clear conclusion
stating that it will actually happen.<br>
<br>
Just one correction - @UpgradeScoped belongs to Servlet spec; If
you would want to introduce something into WebSocket spec, it
would need to be something like @WebSocketSessionScoped; upgrade
is defined in Servlet and if there is any scope derived from it,
it should be there.<br>
<br>
@ViewScoped/@FlowScoped are different - there are specific to JSF.
@UpgradeScoped is specific to Servlet and WebSocket spec just
depends on that.<br>
<br>
Regards,<br>
Pavel<br>
<br>
On 04/12/14 10:17, Antonio Goncalves wrote:<br>
</div>
<blockquote
cite="mid:CA+ZZq99C-n5ezv0h9+A-eH_T-7W26SK7kU-_DsYvRTJu9aJnTw@mail.gmail.com"
type="cite">
<div dir="ltr">Hi
<div><br>
</div>
<div>FYI we are hoping to have no Servlet related topics in the
CDI 2.0 specification. The idea is for other specifications to
use CDI to create their own scope (@ViewScoped/@FlowScoped in
JSF, but also @TransactionScoped in JTA). Following this
logic, the @UpgradeScoped would make sense in the WebSocket
spec.</div>
<div><br>
</div>
<div>Antonio</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Dec 4, 2014 at 9:28 AM, Pavel
Bucek <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:pavel.bucek@oracle.com" target="_blank">pavel.bucek@oracle.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Hello Arjan,<span><br>
<br>
On 03/12/14 19:44, arjan tijms wrote:<br>
</span></div>
<span>
<blockquote type="cite">Hi,<br>
<br>
On Wednesday, December 3, 2014, Pavel Bucek <<a
moz-do-not-send="true"
href="mailto:pavel.bucek@oracle.com"
target="_blank">pavel.bucek@oracle.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
all,<br>
<br>
I'm trying to figure out how to solve issue in JSR
356 - Java API for<br>
WebSocket, related to CDI scope usable from
WebSocket endpoints. Problem<br>
is, that "standard" scopes do not apply, because
there is no<br>
@RequestScoped (http response is already sent),
HttpSession does not<br>
need to be created and the rest does not seem to
be applicable, ...<br>
<br>
I believe that CDI specification should define
@UpgradeScoped, which<br>
would cover usages of HttpUpgradeHandler from
Servlet API. (Similarly as<br>
it does for @RequestScoped, @SessionScoped, ... )</blockquote>
<div><br>
</div>
Wouldn't it be a better option to have WebSocket
define that scope, using CDI to implement it? <br>
</blockquote>
<br>
</span> That is one possibility, but @UpgradeScoped
would be more general than just for WebSocket - it would
apply for all HTTP/1.1+ Upgrade applications. In my
eyes, it is something which was forgotten to do in Java
EE 7 release, since HttpUpgradeHandler was introduced in
it.<br>
<br>
Also please note, that other Servlet related scopes are
already in CDI spec, so it seems like it belongs there
more than anywhere else. This might have multiple
reasons - for example, you can easily define
relationship between @UpgradeScoped and others, already
existing ones. In this sense, CDI specification now
depends on Servlet API (it references some of the
classes defined in it), but Servlet does not do that for
CDI. I don't think that Servlet spec should introduce
similar dependency just because of new scope.<br>
<br>
Thanks,<br>
Pavel<br>
<br>
</div>
<br>
_______________________________________________<br>
cdi-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/cdi-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this list, the provider
licenses the code under the Apache License, Version 2 (<a
moz-do-not-send="true"
href="http://www.apache.org/licenses/LICENSE-2.0.html"
target="_blank">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.<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>
<div dir="ltr">Antonio Goncalves <br>
Software architect, Java Champion and Pluralsight author<br>
<br>
<a moz-do-not-send="true"
href="http://www.antoniogoncalves.org" target="_blank">Web
site</a> | <a moz-do-not-send="true"
href="http://twitter.com/agoncal" target="_blank">Twitter</a>
| <a moz-do-not-send="true"
href="http://www.linkedin.com/in/agoncal"
target="_blank">LinkedIn</a> | <a
moz-do-not-send="true"
href="http://pluralsight.com/training/Authors/Details/antonio-goncalves"
target="_blank">Pluralsight</a> | <a
moz-do-not-send="true" href="http://www.parisjug.org"
target="_blank">Paris JUG</a> | <a
moz-do-not-send="true" href="http://www.devoxx.fr"
target="_blank">Devoxx France</a></div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>