struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10217] - LookupDispatchAction doesn't use new exception handling provided by the standard "execute" of other actions
Date Mon, 15 Jul 2002 07:21:31 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10217>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10217

LookupDispatchAction doesn't use new exception handling provided by the standard "execute"
of other actions

kevin@henrikson.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|DUPLICATE                   |



------- Additional Comments From kevin@henrikson.com  2002-07-15 07:21 -------
Seems the root of this bug about not being able to use the Struts 1.1 Exception 
handling is still here for the *DispatchAction's.  The methods are called by 
dispatchMethod() which contains several catch statments.  If any of the methods 
in my DispatchAction throw an Exception it will get wrapped in a 
InvocationTargetException and caught locally by DispatchAction instead of being 
thrown up the stack to get handled by Action and it's Exception handlers.

If I remove the catch for InvocationTargetException then it will get thrown up 
the stack to be handled by the ExceptionHandler.  The problem I see with this 
is:

  Since any/all Exceptions from the various DispatchAction subclass methods 
will be thrown as an InvocationTargetException it's basically impossbile to 
setup any logic or rules in struts-config.xml to handle different Exceptions.

  I guess with 1.4 we'd be able to call getCause() to get the real cause which 
could then be handled.  Or in 1.3 provide a wrapping exception class to 
simulate getCause in older JVM's.

  Or if it's decided that there is no way around having the try {} catch's in 
DispatchAction then the Java docs should be updated to notify users that 
DispatchAction and it's subclasses can't use the new Struts 1.1 Exception 
handling routines.

--
To unsubscribe, e-mail:   <mailto:struts-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@jakarta.apache.org>


Mime
View raw message