Team,
Do we have a standard way of propagating CDI contexts (request, session,
application, singleton, conversation) and other threadlocal state from a
parent thread say servicing a servlet request to its dispatched child
runnable using the servlet 3.0 AsyncContext.startAsync or the WorkManager
Hi,
i don't know any standard way but what i often saw was to create a kind of
invocation context to avoid to need anything in the async call.
- Romain
2012/6/22 Rohit Kelapure kelap...@gmail.com
Team,
Do we have a standard way of propagating CDI contexts (request, session,
application,
See https://builds.apache.org/job/OpenWebBeans-trunk/856/
Correct. Some code in the container peeks, pushes and pops this JavaEE
context before and after the work has been dispatched.
On Fri, Jun 22, 2012 at 12:24 PM, Romain Manni-Bucau
rmannibu...@gmail.comwrote:
Hi,
i don't know any standard way but what i often saw was to create a kind of
Hi folks!
We are aware that OWB currently doesn't provide this. But all the information
is already centrally collected and maintained in the ContextsService.
For WAS this will most probably be the WebContextsService. So all you need to
know is centrally available there.
Also the TheadLocal
As far as I understood, not really:
..., and then exit from the container on the original thread.
Thus you start the new thread, pass over the context and then exit from the
original thread. - only 1 thread for CDI. It's basically a thread-swapping.
IF this gets done atomically (CDI-1.1 will
