<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    +1 . So far the spec has been listing the situations in which a
    particular context is active. Not in which it is inactive. We should
    carry on with that IMO.<br>
    <br>
    <div class="moz-cite-prefix">On 06/24/2015 04:38 PM, Romain
      Manni-Bucau wrote:<br>
    </div>
    <blockquote
cite="mid:CACLE=7M+HDXJFZeLeFDNZkyaPdkmtZMW1Rt7+-+ga5SRojqTnA@mail.gmail.com"
      type="cite">
      <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 moz-do-not-send="true"
                              href="https://twitter.com/rmannibucau"
                              target="_blank">@rmannibucau</a> |  <a
                              moz-do-not-send="true"
                              href="http://rmannibucau.wordpress.com"
                              target="_blank">Blog</a> | <a
                              moz-do-not-send="true"
                              href="https://github.com/rmannibucau"
                              target="_blank">Github</a> | <a
                              moz-do-not-send="true"
                              href="https://www.linkedin.com/in/rmannibucau"
                              target="_blank">LinkedIn</a> | <a
                              moz-do-not-send="true"
                              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">&lt;<a moz-do-not-send="true"
              href="mailto:antoine@sabot-durand.net" target="_blank">antoine@sabot-durand.net</a>&gt;</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 &lt;<a moz-do-not-send="true"
                      href="mailto:jharting@redhat.com" target="_blank">jharting@redhat.com</a>&gt;
                    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>
                    &gt; Jozef,<br>
                    &gt;<br>
                    &gt; Sorry my question wasn't precise enough. What
                    will be the Request<br>
                    &gt; Context behavior in your implementation of EDR1
                    ?<br>
                    <br>
                  </blockquote>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>