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 caches in the proxies will need to get cleared (if being used). In practice this doesn't make any problems atm, as asynchronous requests must only get performed if ALL involved Servlets, Filters, etc must have <async-supported>true</async-supported> Of course, at the end of the day we should support it! Will take a look once I'm back from the conference next week. LieGrue, strub ----- Original Message ----- > From: Romain Manni-Bucau <[email protected]> > To: [email protected] > Cc: > Sent: Friday, June 22, 2012 6:24 PM > Subject: Re: CDI context propagation for threads spawned asynchronously using > servlet 3.0 and javax.resource.spi.work.WorkManager APIs > > 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 <[email protected]> > >> 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 >> APIs. >> >> I understand that the solution may be specific to individual containers >> like Tomcat, WebLogic, WAS etc ... >> Has anyone already solved this problem for their container ? >> Thought I would ask before fixing it in WAS. >> >> -cheers, >> Rohit Kelapure >> >
