Hi
On 10/10/13 16:12, cvarona wrote:
Hi,
as for cxf 2.7.7, the following AbstractClient code:
prevents important failure information from bubbling up to a place where it
could be more properly logged or dealt with. Wouldn't it be better to use
the WebApplicationException constructor that accepts both a response and an
exception?
I'm actually thinking that code which catches Throwable and rethrows
WebApplicationException is mostly dead, the idea the there is throw the
most specific JAX-RS 2.0 exception (per the spec rules), example, if it
is HTTP 500, then the attempt is made to throw InternalServerErrorException.
That can fail only if a Constructor-based instantiation fails due to
some CL issues, etc so the code resorts to returning a base
WebApplicationException
In your case, what exactly is happening, why do you see the exception
thrown ?
Cheers, Sergey
Kind regards
--
View this message in context:
http://cxf.547215.n5.nabble.com/AbstractClient-convertToWebApplicationException-does-not-preserve-original-exception-tp5734930.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
