Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] InputStreamContentProvider wrapping exceptions

On 3/26/2015 3:03 PM, John Gardiner Myers wrote: wraps failures in a NoSuchElementException, presumably because it can't throw an IOException. Unfortunately, this tends to obscure the real failure.

Would it make sense for ContentCallback.process() to unwrap the NoSuchElementException when it has a cause?

Or perhaps the problem is that Jetty let the exception propagate out of HttpRequest.send() instead of swallowing it somewhere. When it propagates out of HttpRequest.send(), the caller is likely to act on (or propagate) that an not even look at the Listener.

Back to the top