Users Mailing List
Subject: RE: excpetion chaining to custom exception handler issue
Hi Wes,
Appreciate your reply, thanks for checking the issue. I'm sure that my
exception handling action class is not throwing an exception by itself. I have
a general try-catch on that and it never fall
From: Wes Wannemacher [mailto:w...@wantii.com]
Sent: Friday, September 11, 2009 1:32 PM
To: Struts Users Mailing List
Subject: Re: excpetion chaining to custom exception handler issue
Your exception mapping is likely throwing an exception then... think
of it like this -
1 Action gets invoked
2 Oh-No!
Your exception mapping is likely throwing an exception then... think
of it like this -
1 Action gets invoked
2 Oh-No! an exception -> go to the exception page
3 Exception page invoked
4 Oh-No! an exception -> go to #2
Xwork's chain result explicitly checks that an infinite chain sequence
isn't
Anybody have any ides about this??
I try to do an additional action class with redirectAction after the
first chaining using a second action to avoid the 500 error but that
didn't help me, debugging into the ActionChain interceptor from xworks
shows that it went to an infinte error after checking
4 matches
Mail list logo