I don't know too much about it - but wouldn't you be better using a finally clause instead of re-throwing the exception?
Cheers, Scott
Cameron Braid wrote:
When extending the BeforeAfterInterceptor, if the invocation throws an exception, the after method isn't called.
Should the BeforeAfterInterceptor catch the exception, run the after() and then re-throw the exception ?
Any thoughts anyone ?
--
ATLASSIAN - http://www.atlassian.com Expert J2EE Software, Services and Support ------------------------------------------------------- Need a simple, powerful way to track and manage issues? Try JIRA - http://www.atlassian.com/software/jira
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
