On Tue, 16 Mar 2010 08:55:30 -0300, Inge Solvoll
wrote:
Hi!
Hi!
After some time, I got the idea to override the default exception
reporter page with my own, and copy the T5 default code into my new
exception
reporter. Then I started removing parts from it until it stopped
crashing. I
Hi!
Just to wrap this up in case someone needs the information later:
After some time, I got the idea to override the default exception reporter
page with my own, and copy the T5 default code into my new exception
reporter. Then I started removing parts from it until it stopped crashing.
It turne
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 cras
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
I've been struggling quite a while with this problem. On Jetty, the
non-production mode exception page mostly works the first few requests,
after that it starts to crash with the exception listed below. I'm not 100%
sure, but I think it worked on tomcat 6. Our test server is running T5 in
productio
