Yes, I am using that feature for "Unchecked" exceptions. I just have some
a checked exception (UnAuthenticatedException) that I would like to catch
in my filter and this filter will send a redirect to the sso server.
I don't want to do this globally for all exceptions. Just my one
exception "UnAuthenticatedException"
However, thanks for your response.
> Why not create your own exception page?
>
> You can define a method
> public void setException(Throwable value) { ... }
> and Tapestry will call this before activating your exception page.
>
>
>
>
> Phillip Rhodes wrote:
>> I have a checked exception that is thrown from various listeners in my
>> tapestry app. I was hoping that I could use a servlet filter to catch
>> these specific exceptions in order to deal with them.
>>
>> Is this just something that is impossible to do within the tapestry
>> framework due to tapestry having to catch all exceptions for it's error
>> reporting/interfacing with the servlet spec...
>>
>>
>> thanks.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>
> --
> Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr
> Tapestry / Tacos developer
> Open Source / J2EE Consulting
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
