On 3/26/2015 3:03 PM, John Gardiner Myers wrote:
InputStreamContentProviderIterator.next() 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.
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users
