[cdi-dev] Contexts behavior in SE and Async Event for EDR1

Romain Manni-Bucau rmannibucau at gmail.com
Thu Jun 18 09:13:23 EDT 2015


I wouldn't activate any "web" scope by default, in particular for async
events where I think most of the time it will not be used. Next feature
request will be to inherit the scope between async threads....and here I
guess we agree it will not go very far.

Side note: using request scope where actually a thread scope is needed is a
pain, maybe time to add a thread scoped with an accessible manual
activation. Would make "batches", "timers" etc easy to impl/integrate.

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber

2015-06-18 15:10 GMT+02:00 Antoine Sabot-Durand <antoine at sabot-durand.net>:

> Hi guys,
> We should finally decide how to manage normal scope context (other than
> application context ) in SE and during Async Event for EDR1.
> Having only RequestContext active during async event  as Martin suggest in
> the PR makes sense and would be consistent with its behavior during async
> EJB call.
> Mark asked twice to activate Request Context all the time in SE (making it
> a new Application Context). I’m not found of it, but I’ml not the only one
> to decide here.
> What is you feeling about this ?
> Antoine
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20150618/9310da0b/attachment.html 

More information about the cdi-dev mailing list