[cdi-dev] Contexts behavior in SE and Async Event for EDR1
atsticks at gmail.com
Fri Jun 19 18:51:21 EDT 2015
for me the question is: do we need a RequestContext? We have the Event
payload, which is shared (and AFAIK also still mutable) and can be used to
represent the common context as well, for both synch or asynch event cases.
Adding a parallel "context" does not necessarily make things easier IMO,
because you have to exactly define what a request in that sense is, when
does it start, where does it end, how it is propagated/stacked etc. So my
question is: what is the benefit of defining the request scope additional
to the event payload already in place?
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 ?
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> 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.
Java Engineer & Architect, JSR Spec Lead
CH - 8620 Wetzikon
*Switzerland, Europe Zurich, GMT+1*
*Google: atsticksMobile +41-76 344 62 79*
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cdi-dev