RE: [OS-webwork] BeforeAfterInterceptor

[Jason Carreira]

Title: Message

I don't think this is good to do as a general rule. Most times you want to stop processing when an exception occurs. You could implement this behavior with a couple of carefully placed interceptors.

-----Original Message-----
From: Cameron Braid [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 5:08 AM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] BeforeAfterInterceptor

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 ?