|Re: [jetty-users] InputStreamContentProvider wrapping exceptions
On 3/30/2015 6:50 AM, Simone Bordet wrote:
Jetty client does swallow the exception and fails the callback, resulting in the complete event being triggered, see HttpSender.send[Headers|Content]() catch-all block. The unwrapped exception actually tells me that it happened while you were reading the request content of a request to a server, so you're actually using Jetty's HttpClient as a kind of proxy. I would not have known that by just reading the unwrapped exception, so seems even useful to me...The class of the wrapper is confusing, if not actively misleading. The failure was not a programming error, it was the failure of a ContentProvider to produce content. If the wrapper were of a class, say, ContentProviderExecutionException then that would be a lot more informative.
Back to the top