+1
let's move on with AHC...
since all the overhead (default sender etc) goes away, switching the
underlying impl is not hard, in the future..
On Thu, Jul 11, 2013 at 3:23 PM, Sebastien Blanc <scm.blanc(a)gmail.com>wrote:
Ok just an update :
RestEasy client seems to be a mess when beeing used inside an app deployed
on a JBoss AS app , pretty lame :/ See this thread :
http://sourceforge.net/mailarchive/forum.php?thread_name=51DE9678.9060103...
Having to modify your module settings on AS level just to have to use the
JAva Sender API is for me is total no go ....
For this reason I plan to swtich back to the Http Async Client impl, wdyt
?
Seb
On Wed, Jul 10, 2013 at 5:00 PM, Matthias Wessendorf <matzew(a)apache.org>wrote:
>
>
>
> On Wed, Jul 10, 2013 at 4:45 PM, Douglas Campos <qmx(a)qmx.me> wrote:
>
>> On Wed, Jul 10, 2013 at 09:41:48AM +0200, Sebastien Blanc wrote:
>> > I discussed a bit with Matzew and we agreed that we should probably
>> remove
>> > the AsyncHttpClient implementation and just keep the resteasy client,
>> wdyt
>> > ?
>> Will resteasy client work fine outside of EAP/Wildfly?
>>
>
> yep - works on JavaSE. It's basically a wrapper around Apache Http Client.
>
> On the Unit test (for the java sender) I was using it to send messages
> from there (before we added the mocking)
>
>
>>
>> --
>> qmx
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog:
http://matthiaswessendorf.wordpress.com/
> sessions:
http://www.slideshare.net/mwessendorf
> twitter:
http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev