Yes, the generated code catches the thrown exception and wraps it.
On Mon, Feb 9, 2009 at 1:24 PM, Ulrich Stärk <u...@spielviel.de> wrote:
> This probably happens during class transformation. I'd look somewhere in the
> o.a.t.transform packages.
>
> Uli
>
> manuel aldana schrieb:
>>
>> Hi,
>>
>> when a custom component throws a checked Exception it seems to be handled
>> by a kind of Interceptor, but I cannot find it while debugging or looking at
>> source code. I am sure there is some higher exception wrapping magic
>> involved here (though I haven't found any Interceptor or AOP style
>> wrapping)...
>>
>> This checked exception gets intercepted:
>> -----
>> class Comp{
>> @BeginRender
>> void renderMessage(MarkupWriter writer) throws Exception{
>> throw new CheckedException();
>> }
>> }
>> ----
>>
>>
>> This unchecked exception does not get intercepted:
>> ----
>> class Comp{
>> @BeginRender
>> void renderMessage(MarkupWriter writer) {
>> throw new UncheckedException();
>> }
>> }
>> ----
>>
>> thanks.
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
