Hmmm... I thought exceptions on Exception page were thrown unchanged,
but that's not true... they're also wrapped in an
ApplicationRuntimeException.
So, if you want some of your exceptions to be thrown out of the Tap servlet
and caught by a filter, you'd have to use a custom
org.apache.tapestry.er
in pageBeginRender of your custom exception page,
check if the execption is of type UnAuthenticatedException
and if it is, throw it again!
Phillip Rhodes wrote:
> Yes, I am using that feature for "Unchecked" exceptions. I just have some
> a checked exception (UnAuthenticatedException) that I woul
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 "UnA
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
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
