I'm having this interface
@POST
@Path("/bla")
Response proxy(InputStream entity) throws IOException;
In the implementation, I am able to read from the stream, except if the
Content-Type of the POST was application/x-www-form-urlencoded.
I guess that is because resteasy already has co
I use a ClientInterceptor for that (the code also takes care of basic auth,
timeouts and ssh-without-hostname-verification).
ApacheHttpClient4Executor ex = new
ApacheHttpClient4Executor(getBasicAuthClient(LOGIN,PASS,
"application/json", null, new
SingleClientConnManager(getSSHBypassSch
When creating a resource (POST /items) i was a bit annoyed by the fact
that my implementation has a dependency on jax-rs classes: it uses
response builder to build a 201 response. This also pollutes my
service interface, since the return value has to be a Response.
To fix this, i introduced an ann
nterested in a
> callback?
>
> On 7/5/12 6:14 AM, Dieter Cailliau wrote:
>> We have a scenario where some client is initiating an HTTP POST to the
>> server, the server responds with a 201, but this response is not
>> acknowledged (tcp) by the client (because of some
We have a scenario where some client is initiating an HTTP POST to the
server, the server responds with a 201, but this response is not
acknowledged (tcp) by the client (because of some communication stack
error) (we know this because we used wireshark to trace the tcp
communication). I think this
I'm wondering why resteasy (2.2.2) contains a jgroups 2.6.13 jar; is
this an optional dependency / can i remove / upgrade it? What is it
used for?
--
Live Security Virtual Conference
Exclusive live event will cover all the
I created this little filter to automatically return a 304 if the
"If-None-Match" filter matches the ETag.
It's not clear to me however, how i can now prevent the entity to be
written to the output stream, wile preserving the response headers.
public class NotModifiedFilter implements Filter {
We have an application that talks to remote rest-api's, using resteasy
client framework.
Our code creates a new proxy for each call, and these calls run on new
threads always (we don't cache our client proxies, and the threads are
from a threadpool that is created and shutdown afterward).
We suffe