Thanks Remi, I'll combine them both then. At least with the Stripes
exception handling I get to fire off internal emails about the issue.
On Tue, Apr 2, 2013 at 11:43 AM, Remi VANKEISBELCK wrote:
> Note that when using request.getDispatcher() it's boiling down to the
> container "crapping out"
Note that when using request.getDispatcher() it's boiling down to the container
"crapping out" :P
Could happen e.g. if you try to dispatch to a non existing resource or stuff
like that.
If you wanna avoid this entirely then wrap everything in a try/catch in your
Stripes exception handler. Then
So if I want to hide the stack trace output entirely, I still need a
handler defined by ... in web.xml just in case
the Stripes exception handling mechanism craps out then?
On Tue, Apr 2, 2013 at 4:24 AM, Remi VANKEISBELCK wrote:
> Hi Chris,
>
> It only declares IOException and ServletExceptio
Hi Chris,
It only declares IOException and ServletException because the handler itself
may fail (e.g. call to request.getDispatcher()), or so that, in case you want
to, you can re-throw an exception that matches the servlet spec, and then let
the container handle it.
HTH
Remi
Le 2 avr. 2013
I'm a little confused at the unhandled exception handling mechanism.
The documentation gives an example on how to get implement a handler for it
(http://www.stripesframework.org/display/stripes/Exception+Handling) and I
am looking at the bottom example which gives access to the action bean that
tr
