<p dir="ltr"><br>
Le 7 mars 2016 08:35, "Martin Kouba" <<a href="mailto:mkouba@redhat.com">mkouba@redhat.com</a>> a écrit :<br>
><br>
> Dne 6.3.2016 v 15:39 Romain Manni-Bucau napsal(a):<br>
><br>
>> Hi guys,<br>
>><br>
>> as a user having a ComlpetionStage makes me loose some JDK utilities,<br>
>> can we move back to CompletionFuture?<br>
>><br>
>> It would allow for instance:<br>
>><br>
>> // doesn't work with CompletionStage<br>
>> CompletionFuture.allOf(event1.fireAsync(...), event2.fireAsync(...))<br>
>> .then(...)<br>
><br>
><br>
> Well, this should work if the underlying CompletionStage impl supports toCompletableFuture(), i.e. in Weld 3:<br>
></p>
<p dir="ltr">Yes but it is not natural to convert it IMO = we can do better</p>
<p dir="ltr">> CompletableFuture.allOf(event1.fireAsync(...).toCompletableFuture(), event2.fireAsync(...).toCompletableFuture())<br>
><br>
> 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.<br>
></p>
<p dir="ltr">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</p>
<p dir="ltr">><br>
>><br>
>> Romain Manni-Bucau<br>
>> @rmannibucau <<a href="https://twitter.com/rmannibucau">https://twitter.com/rmannibucau</a>> | Blog<br>
>> <<a href="http://rmannibucau.wordpress.com">http://rmannibucau.wordpress.com</a>> | Github<br>
>> <<a href="https://github.com/rmannibucau">https://github.com/rmannibucau</a>> | LinkedIn<br>
>> <<a href="https://www.linkedin.com/in/rmannibucau">https://www.linkedin.com/in/rmannibucau</a>> | Tomitriber<br>
>> <<a href="http://www.tomitribe.com">http://www.tomitribe.com</a>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> cdi-dev mailing list<br>
>> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
>><br>
>> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br>
>><br>
><br>
> -- <br>
> Martin Kouba<br>
> Software Engineer<br>
> Red Hat, Czech Republic<br>
</p>