I hope I'm doing something wrong here. The short version is that I'm
building a service that's going to be fetching a lot of potentially
too-large-for-GAE resources, so I need to gracefully handle
ResponseTooLargeException.
Given a snippet like this:
try {
theURL = new URL(url);
inStream = theURL.openStream();
byteReturn = readInputStream(inStream);
} catch(ResponseTooLargeException e) {
throw new ImageValidationException("Image was too large"); //custom
exception
} catch(IOException .... //finally, etc.
Upon deploy, this wouldn't catch and continued triggering uncaught
servlet exceptions. It was only once I started catching
ResponseTooLargeException's parent RuntimeException that the catch
executed and threw the appropriate application Exception.
Thoughts on why this is?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---
