<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I agree. The EDR is supposed to be a draft for review. It’s not supposed to be production ready.<div class=""><br class=""></div><div class="">Add a note saying “OPEN ISSUE: We need to provide the ability to start the request scope”.</div><div class=""><br class=""></div><div class="">In Weld, you can add a release note saying how to do it in Weld.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 24 Jun 2015, at 10:38, Romain Manni-Bucau <<a href="mailto:rmannibucau@gmail.com" class="">rmannibucau@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">What happen if we say nothing? will not hurt later IMHO</div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""><span style="font-size:small" class="">Romain Manni-Bucau</span><br class=""><a href="https://twitter.com/rmannibucau" target="_blank" class="">@rmannibucau</a> | <a href="http://rmannibucau.wordpress.com/" target="_blank" class="">Blog</a> | <a href="https://github.com/rmannibucau" target="_blank" class="">Github</a> | <a href="https://www.linkedin.com/in/rmannibucau" target="_blank" class="">LinkedIn</a> | <a href="http://www.tomitribe.com/" target="_blank" class="">Tomitriber</a></div></div></div></div></div></div></div></div></div></div>
<br class=""><div class="gmail_quote">2015-06-24 16:28 GMT+02:00 Antoine Sabot-Durand <span dir="ltr" class=""><<a href="mailto:antoine@sabot-durand.net" target="_blank" class="">antoine@sabot-durand.net</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">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 class=""><div class="gmail_quote"><div dir="ltr" class="">Le mer. 24 juin 2015 à 16:22, Jozef Hartinger <<a href="mailto:jharting@redhat.com" target="_blank" class="">jharting@redhat.com</a>> a écrit :<br class=""></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 class="">
<br class="">
For @RequestScoped there is no natural notion of a request in plain Java<br class="">
SE. It's the user that needs to set the boundaries of a task that the<br class="">
@RequestScope is supposed to represent. This can be done using Weld API<br class="">
and hopefully using ContextControl soon. In the meantime I see no point<br class="">
in blurring this with magical contexts that try to guess what the use wants.<br class="">
<br class="">
That means that the context is not active by default but can be<br class="">
controlled using the API.<br class="">
<br class="">
On 06/24/2015 03:56 PM, Antoine Sabot-Durand wrote:<br class="">
> Jozef,<br class="">
><br class="">
> Sorry my question wasn't precise enough. What will be the Request<br class="">
> Context behavior in your implementation of EDR1 ?<br class="">
<br class="">
</blockquote></div>
</div></div></blockquote></div><br class=""></div>
_______________________________________________<br class="">cdi-dev mailing list<br class=""><a href="mailto:cdi-dev@lists.jboss.org" class="">cdi-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/cdi-dev<br class=""><br class="">Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.</div></blockquote></div><br class=""></div></body></html>