<div dir="ltr"><div>Hi Romain,</div><div><br></div>I am not sure, I have fully understand how an observer with <span style="font-size:12.8000001907349px">CompletableFuture could look like. Could you give us an example? </span><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">Afair </span><span style="font-size:12.8000001907349px">CompletableFuture</span><span style="font-size:12.8000001907349px"> was considered to be used in the "trigger" side in order to track async event invocation completion.</span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">br, Sven</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-03-31 18:00 GMT+02:00 Romain Manni-Bucau <span dir="ltr"><<a href="mailto:rmannibucau@gmail.com" target="_blank">rmannibucau@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi guys,<div><br></div><div>on async topic if I followed we are at the point where we are looking for an activation on the observer side.</div><div><br></div><div>Since Java 8 has now CompletableFuture it would be great to use it. Today the spec doesnt use observer returned values so it is mainly a bad practise to have one even if not strictly forbidden - BTW never saw it in real applications - plus spec is not compatible - not specified at all - with CompletableFuture since it is a new API so we can use it as a marker.</div><div><br></div><div>This is quite interesting for few reasons:</div><div>1- we have our double activation</div><div>2- API is user friendly (observer is async and has an async signature)</div><div>3- open door for future async enhancements (hopefully not in CDI) with composition of these observers</div><div><br></div><div><br></div><div>Only point I'm not sure is should these observers support sync events. I don't see anything blocking to do it but can have missed something.</div><div><br></div><div><br></div><div>wdyt?</div><span class="HOEnZb"><font color="#888888"><div><br clear="all"><div><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br><span style="font-size:small">Romain Manni-Bucau</span><br><a href="https://twitter.com/rmannibucau" target="_blank">@rmannibucau</a> | <a href="http://rmannibucau.wordpress.com" target="_blank">Blog</a> | <a href="https://github.com/rmannibucau" target="_blank">Github</a> | <a href="https://www.linkedin.com/in/rmannibucau" target="_blank">LinkedIn</a> | <a href="http://www.tomitribe.com" target="_blank">Tomitriber</a></div></div></div></div></div></div></div></div></div></div>
</div></font></span></div>
<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" target="_blank">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" target="_blank">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></blockquote></div><br></div>