But in addition our exception handler extracts redirect destination from our custom exception and performs redirect. 16.01.2014 17:08 пользователь "Thiago H de Paula Figueiredo" < thiag...@gmail.com> написал:
> On Thu, 16 Jan 2014 10:41:55 -0200, Andrey <andreus...@gmail.com> wrote: > > Finally we've solved spam problem (but my collegues are not very happy >> with >> this entire approach): >> we use log4j matcher to skip error log message from RenderQueueImpl, and >> log it if needed in our exception handler. >> >> p.s. getters do not help, because they will throw exceptions too when >> data unavailable. >> > > Then this is normal exception handling. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
