[cdi-dev] Enhancing SPI to support async operation for contexts

Romain Manni-Bucau rmannibucau at gmail.com
Thu Feb 19 08:19:23 EST 2015

+1 excepted for servlet requests where we can significantly do better
but that's surely better to deal with it in another thread?

Romain Manni-Bucau

2015-02-19 14:18 GMT+01:00 Jozef Hartinger <jharting at redhat.com>:
> I agree with Romain that we cannot change the semantics of existing
> contexts.
> Furthermore, I think that instead of these tricky context propagations
> we should promote async event-driven architecture where as much state as
> needed is carried within the message / event payload itself instead of
> clients relying on state from context, threadlocal, etc.
> Jozef
> On 02/19/2015 10:32 AM, Antoine Sabot-Durand wrote:
>> Hi All,
>> Beyond the asynchronous event case, shouldn’t we provide a way for user to launch async treatments in CDI with the possibility to keep the existing contexts at the moment of async operation launch?
>> Today servlet or JAX-RS spec support async call without the loss of request for instance. Shouldn’t we think to something like that?
>> Thanks for your input on that point.
>> 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.

More information about the cdi-dev mailing list