I've been wondering about that myself :) It's probably something related to the fact that I've got Struts 1, T4 and T5 running together.
So what you're saying is that I've probably put something in the session that has a bad toString(). I guess that's why it often works a few times before it crashes... On Wed, Mar 3, 2010 at 9:34 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > Tapestry 5.1 error page fails when something in the session has a > toString() or a getter method that throws some exception when invoked. > > > Caused by: java.lang.NullPointerException >> at >> org.apache.jasper.compiler.TagLibraryInfoImpl.toString(TagLibraryInfoImpl.java:127) >> > > Why would a JSP compiler appear in the middle of your Tapestry stack trace? > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, software architect and developer, 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 > >
