I cannot accept this pull request as it will break JAX-RS TCK tests. If
you want to add a configuration switch to automatically close the
connection, thats fine, but the default needs to keep it open as this is
required by the specification.
On 10/21/2013 4:52 PM, Anthony Whitford wrote:
> I c
I created a fix for this issue by modifying the error handling of the
ClientInvocation.extractResult method.
See Pull Request: https://github.com/resteasy/Resteasy/pull/397
My primary concern about catching WebApplicationException all over the place is
that it seems to violate Separation of Co
Unfortunately, you are responsible for cleaning up the connection
yourself. You must do:
try {
... do something with client ...
} catch (WebApplicationException ex) {
ex.getResponse().close();
}
This is because the response may contain an entity that the user wants
to access. I'm pret
I discovered a particularly nasty problem using the Resteasy Client Framework
and have documented it in the issue tracker:
https://issues.jboss.org/browse/RESTEASY-963
In a nutshell, if a Client Proxy instance makes a call to the service and the
service throws an exception, the Client is now r
