<div dir="ltr">What happen if we say nothing? will not hurt later IMHO</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br><span style="font-size:small">Romain Manni-Bucau</span><br><a href="https://twitter.com/rmannibucau" target="_blank">@rmannibucau</a> | <a href="http://rmannibucau.wordpress.com" target="_blank">Blog</a> | <a href="https://github.com/rmannibucau" target="_blank">Github</a> | <a href="https://www.linkedin.com/in/rmannibucau" target="_blank">LinkedIn</a> | <a href="http://www.tomitribe.com" target="_blank">Tomitriber</a></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">2015-06-24 16:28 GMT+02:00 Antoine Sabot-Durand <span dir="ltr"><<a href="mailto:antoine@sabot-durand.net" target="_blank">antoine@sabot-durand.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Ok, but now in the chapter I have mention for Session Scope and conversation Scope not being active in SE. Wouldn't it be strange to have no mention of Request Scope or should we make a "temp hack" saying that session scope is not active...</div><div class="HOEnZb"><div class="h5"><br><div class="gmail_quote"><div dir="ltr">Le mer. 24 juin 2015 à 16:22, Jozef Hartinger <<a href="mailto:jharting@redhat.com" target="_blank">jharting@redhat.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Depends on the spec mostly.<br>
<br>
For @RequestScoped there is no natural notion of a request in plain Java<br>
SE. It's the user that needs to set the boundaries of a task that the<br>
@RequestScope is supposed to represent. This can be done using Weld API<br>
and hopefully using ContextControl soon. In the meantime I see no point<br>
in blurring this with magical contexts that try to guess what the use wants.<br>
<br>
That means that the context is not active by default but can be<br>
controlled using the API.<br>
<br>
On 06/24/2015 03:56 PM, Antoine Sabot-Durand wrote:<br>
> Jozef,<br>
><br>
> Sorry my question wasn't precise enough. What will be the Request<br>
> Context behavior in your implementation of EDR1 ?<br>
<br>
</blockquote></div>
</div></div></blockquote></div><br></div>