<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 4/5/2016 8:32 AM, Stian Thorgersen
wrote:<br>
</div>
<blockquote
cite="mid:CAJgngAdzzDAN4Fb1KboPegLExOgfoow4ZoitxO7UfOZ8v3bb+Q@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 5 April 2016 at 14:19, Bill Burke
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class=""> <br>
<br>
<div>On 4/5/2016 7:47 AM, Marek Posolda wrote:<br>
</div>
<blockquote type="cite"> <br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span>
<blockquote type="cite">
<div dir="ltr">
<div><font face="arial, helvetica,
sans-serif">2) Use JAX-RS 2
client</font></div>
</div>
</blockquote>
</span><font face="arial, helvetica,
sans-serif">+1<br>
<br>
But it will be good if people have
possibility to configure the details
of underlying Apache HTTP Client
(connection pooling, connection/socket
timeouts, tls etc). If it's possible
to achieve it and use JAX-RS 2 client
at the same time, it will be cool.
Otherwise if we need to choose just
one of these, the "configurability" of
Apache HTTP client is more important
IMO.<br>
</font></div>
</blockquote>
<div><br>
</div>
<div>Sticking with RestEasy Client makes the
assumption that all users use other JBoss
projects. We know that's not true as
Tomcat, Jetty and Spring adapters all have
a lot of use. IMO we should either convert
to JAX-RS 2 client or use Apache HTTP
client directly (I'm not to keen on that
though).<br>
</div>
</div>
</div>
</div>
</blockquote>
At least we may just have possibility to inject
underlying <a moz-do-not-send="true"
href="http://javax.ws.rs" target="_blank">javax.ws.rs</a>.<span
style="background-color:#e4e4ff">client.Client
during creation of admin-client. So if someone is
on resteasy and wants to tweak Apache HTTP Client,
he can use RestEasy API to build client by himself
and inject it. If he's using some other library,
he would need to use it's API to build client (and
possibly configure connection pooling etc in
library specific way).<br>
<br>
</span></blockquote>
</span> If you're using Tomcat, Spring or whatever,
anything JBoss is evil and they can't co-exist? That's
ridiculous. You're really going to stub out every
single piece of the REST api and/or write your own
tool? No....<br>
</div>
</blockquote>
<div><br>
</div>
<div>What's wrong with JAX-RS 2.0?</div>
<div> </div>
</div>
</div>
</div>
</blockquote>
The proxy thing is Resteasy specific. Its not in the spec.<br>
<br>
<blockquote
cite="mid:CAJgngAdzzDAN4Fb1KboPegLExOgfoow4ZoitxO7UfOZ8v3bb+Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <br>
We revise the rest interface. Either use Resteasy, or
they can write their own clients.</div>
</blockquote>
<div><br>
</div>
<div>What are you saying here exactly?</div>
</div>
</div>
</div>
</blockquote>
<br>
That we use Resteasy to create the admin client. If somebody
doesn't want to have a dependency on Resteasy then they are on their
own.<br>
<br>
<pre class="moz-signature" cols="72">--
Bill Burke
JBoss, a division of Red Hat
<a class="moz-txt-link-freetext" href="http://bill.burkecentral.com">http://bill.burkecentral.com</a></pre>
</body>
</html>