Thiago, Thanks for the rapid reply. While putting together a test case to send you (the actual code is very long and complex), I figured out this was an error on my part.
Basically, I assumed the exception was being thrown by one method, when in fact it was being thrown by a different method Obviously I need to take a break! Best, George On Tue, Apr 3, 2012 at 2:38 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Tue, 03 Apr 2012 18:34:11 -0300, George Ludwig <georgelud...@gmail.com> > wrote: > > Hi all, >> > > Hi! > > > The problem is that when an Exception is thrown during the calculation of >> the number, Tapestry detects that an Exception was thrown even though it >> was gracefully handled, and throws a TapestryException. This completely >> de-rails my own Exception handling. >> >> Is this considered correct behavior? >> > > No. Full page code and stack trace please. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br >
