On May 12, 2005, at 9:43 PM, Ben Eng wrote:
In your terms my post-listener event is fired only if the original listener succeed without thrown an exception or if throws Page/RedirectException. I don't think an "after" listener event could be coded in your contribution to do that. Please correct me if I'm wrong.
The "after" listener event is fired in a finally, so it should be ok. Perhaps it would be worthwhile catching any exception and passing it in the event.
But that isn't ok in my use-case. I do not want the after listener fired in the event of an error. However, there are two exceptions which are not errors - PageRedirectException and RedirectException. See what I mean?
Alternatively, as you mention if the after event could be given the exception to base its behavior on, that would also work in my case.
Again, it's ultimately up to Howard on whether your approach is the right fit for 4.0 or not. It would seem that a HiveMind interceptor scheme would be a more integrated fit for 4.0.
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
