JIRA ticket, I mean<span></span><br><br>On Wednesday, July 10, 2013, Matthias Wessendorf  wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">there is a bug on that :-)<span></span><br>
<br>On Wednesday, July 10, 2013, Sebastien Blanc  wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Okay,<div>
I will open a jira for this and seems like smart to do this before working on the fluent Message API.</div><div>Seb</div><div><br></div></div><div><br><br><div>
On Wed, Jul 10, 2013 at 10:14 AM, Matthias Wessendorf <span dir="ltr">&lt;<a>matzew@apache.org</a>&gt;</span> wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br><br>On Wednesday, July 10, 2013, Sebastien Blanc  wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div>
<br><br><div>
On Wed, Jul 10, 2013 at 9:52 AM, Matthias Wessendorf <span dir="ltr">&lt;<a>matzew@apache.org</a>&gt;</span> wrote:<br>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div><br><br><div><div><div>On Wed, Jul 10, 2013 at 9:41 AM, Sebastien Blanc <span dir="ltr">&lt;<a>scm.blanc@gmail.com</a>&gt;</span> wrote:<br>





<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Folks ! <div>As you know the current Java Sender API comes today with 2 different implementations : </div>



<div><br></div><div>- Resteasy client (used by default)</div><div>- AsyncHttpClient</div>
<div><br></div><div>I discussed a bit with Matzew and we agreed that we should probably remove the AsyncHttpClient implementation and just keep the resteasy client, wdyt ? </div></div></blockquote><div><br></div><div><br>





</div></div></div><div>yep, I&#39;d prefer one client (based on RestEasy). Also that means we don&#39;t need all the JavaSender, DefaultSender etc...</div></div></div></div></blockquote><div>+1 </div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




<div dir="ltr"><div><div><div><br></div><div>We just have one client, and need to name it &quot;reasonably&quot;.  </div></div></div></div></blockquote><div>Yea how should we name it ?  </div>


<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>
<div><br></div><div>I&#39;d also argue that we should worry that the client can be injected, using CDI. Makes sense when being used on JavaEE backends</div></div></div></div></blockquote><div>isn&#39;t that the responsability of the backend app using the sender or is there anything to do on the sender side ? (in the latest case a jira would be cool)</div>



</div></div></div></blockquote><div><br></div><div><br></div></div><div>it is possible to write the class in a way, that CDI container can not create a proxy</div><div><br></div><div>See last &quot;bug&quot; from Christos<span></span></div>


<div><div>
<div> </div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>
<div> </div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><br></div><div> </div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div dir="ltr"><div><br></div><div>
Seb</div><div><br></div></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a>aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><span><font color="#888888"><br></font></span></blockquote></div><span><font color="#888888"><br>




<br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br>
<br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>





twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</font></span></div></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a>aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div></div>
</blockquote><br><br>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>



twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>
</div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br></blockquote></div></div></blockquote><br><br>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.word</a></blockquote>
<br><br>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a><br>