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

Le 7 mars 2016 08:35, "Martin Kouba" <mkouba(a)redhat.com&gt; a écrit : toCompletableFuture(), i.e. in Weld 3: Yes but it is not natural to convert it IMO = we can do better event2.fireAsync(...).toCompletableFuture()) > AFAIK the default async execution facility of CompletableFuture is ForkJoinPool.commonPool() which is not a good fit for Java EE. Using the CompletionStage interface allows us to wrap the async calls without the specified executor (e.g. CompletionStage.thenApplyAsync(Function<? super T, ? extends U>)) and supply a default one provided by the impl. Should use the pool in which the evznt is fired then "then step" is synchronous is my sample so all is decided at fire time >>> Romain Manni-Bucau >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> <http://rmannibucau.wordpress.com> | Github >> <https://github.com/rmannibucau> | LinkedIn >> <https://www.linkedin.com/in/rmannibucau> | Tomitriber >> <http://www.tomitribe.com>>>>> _______________________________________________ >> cdi-dev mailing list >> cdi-dev(a)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. >> -- > Martin Kouba > Software Engineer > Red Hat, Czech Republic