You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@struts.apache.org by Kris Schneider <kr...@dotech.com> on 2002/10/23 15:02:16 UTC

Re: DispatchAction and declarative exception handling

When this thread:

http://marc.theaimsgroup.com/?l=struts-user&m=102710542128639&w=2

was started a few months back, I passed it over because it seemed to be 1.1-
centric (and it was eventually fixed within a couple of weeks). However, a 
similar issue exists in 1.0.2 that I just stumbled across. I submitted a bug 
and suggested fix for it last night:

http://issues.apache.org/bugzilla/show_bug.cgi?id=13864

In the 1.0.2 case, the way that DispatchAction handles an 
InvocationTargetException seems to make it impossible for an app to use the 
standard servlet error handling mechanism. If the dispatched method throws any 
exception, DispatchAction generates an interanal server error. Well, I suppose 
you *could* still hook up an error page for a 500 status code, but that seems a 
bit limiting ;-). Personally, I'd love to see a 1.0.3 release just for this 
fix, but I may be biased by our team's use of both DispatchAction and error 
pages...

-- 
Kris Schneider <ma...@dotech.com>
D.O.Tech       <http://www.dotech.com/>

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>