<div dir="ltr">Hi,<br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 4, 2017 at 11:17 AM, Martin Kouba <span dir="ltr"><<a href="mailto:mkouba@redhat.com" target="_blank">mkouba@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Well, it works similar to how @Dependent stateless session beans work.<br>
Unlike @RequestScoped there is no real CDI context just a special proxy<br>
that delegates to SPI.</blockquote><div><br></div><div>Indeed, it can't be really request scope, since the principal can potentially change many times during a request. Though, once initially set it normally applies for the remainder of the web request. For other usages of the request scope it's not so well defined in EE actually.</div><div><br></div><div>Talking about this build-in bean though, wouldn't it be a good idea to let JSR 375 take ownership of it? The CDI spec before proposed to the servlet spec to take ownership of the build-in beans for the Servlet owned artefacts (such as HttpServletRequest).</div><div><br></div><div>Kind regards,</div><div>Arjan Tijms</div><div><br></div><div> </div></div></div></div>