Have you looked at the link I've posted in my first message? :) I know I can override the error page. But I like the default one. I just don't like its default behavior which only relies on PRODUCTION_MODE symbol. What I suggest is to change this behavior and analyze if the user that get this exception is a local user. And if its a local user show him error page just like it was in non-production mode. This is what RemoteOnly mode means in ASP.NET.
On Fri, Aug 27, 2010 at 16:19, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Fri, 27 Aug 2010 09:13:41 -0300, Dmitry Gusev <dmitry.gu...@gmail.com> > wrote: > > Yes, I should say test. >> I didn't mean running java debugger. >> I mean trying to reproduce some test case using browser and getting >> exception page. >> > > You can override the error page (which I recommend, anyway), use the logic > you want for showing or not the stack trace and use the ExceptionDisplay > component to show the exception. > > > -- > 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 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Dmitry Gusev AnjLab Team http://anjlab.com
