I am having difficulty using a custom filter to capture remote
exceptions. All requests for our application are filtered through a
class called "ErrorFilter". If the exception is a client-side error, the
filter takes care of the exception handling and forwards to the
appropriate trouble report jsp. If the exception is remote (in
particular, if the requested server object is not available), the
exception never finds it's way completely back to the ErrorFilter, and
the rendered page simply displays the error message.
It is possible that our application code swallows the exception
somewhere (though I've scoured it again and again). I am wondering if
there is something in the Struts framework that would cause this type of
scenario.
Thanks,
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
