[cdi-dev] async: back to completion future?

Reza Rahman reza_rahman at lycos.com
Sun Mar 6 10:37:15 EST 2016

How much end user feedback has there been on this? I have to be honest that it surprises me to find this out now.

This to me stands out as an obvious usability problem. CompletableFuture is the obvious top level end user API, not CompletionStage. Not going with CompletableFuture is very likely to confuse most people. The last thing we need is more potential usability problems in Java EE APIs.

> On Mar 6, 2016, at 9:39 AM, Romain Manni-Bucau <rmannibucau at gmail.com> wrote:
> Hi guys,
> as a user having a ComlpetionStage makes me loose some JDK utilities, can we move back to CompletionFuture?
> It would allow for instance:
> // doesn't work with CompletionStage
> CompletionFuture.allOf(event1.fireAsync(...), event2.fireAsync(...))
>       .then(...)
> Romain Manni-Bucau
> @rmannibucau |  Blog | Github | LinkedIn | Tomitriber
> _______________________________________________
> 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/20160306/01f28196/attachment.html 

More information about the cdi-dev mailing list