I did some testing locally, and it looks to me like exceptions should
be propagated properly. Are you sure that the exception is not handled
somewhere else? From your logs, it appears that error is returned
somewhere along the chain.
Nils-H
On Wed, Apr 16, 2008 at 12:46 AM, Parker Grimes [EMAIL
My interceptor is being called, but it appears that
com.opensymphony.xwork2.interceptor.ExceptionMappingInterceptor is still
being called before my interceptor, despite having my interceptor declared
first in the stack. As you can tell my interceptor is handed the error
result rather than catching
The default ExceptionMappingInterceptor is closer to the error (as
it is configured by default), so it will intercept it first (on the
way out... [1]). If you already have configured exception mappings for
that interceptor, it will never reach your interceptor. It might be
better for you to
Thanks for your help I had an ah ha moment. I know I read that the stack
gets passed through twice, once down the stack and then back up but I had
forgotten that. That was my problem. The exception was being thrown on the
way back up the stack and being caught by the default
4 matches
Mail list logo
