.1045711.n5.nabble.com/Exceptions-during-registry-startup-tp2431019p2845126.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e
I think you are correct, the best thing would be to let the exception
bubble up to the top, preventing the Registry from starting up.
On Fri, Apr 24, 2009 at 3:24 AM, Alfie Kirkpatrick
alfie.kirkpatr...@ioko.com wrote:
Hi, I am staring at an error in my log:
11:02:22.617 [main] ERROR
What's the status on this? Seems the problem still exists in 5.2. No matter
which log level I choose, I never see stack traces of exceptions thrown from
a module's @Startup method.
Cheers,
Peter
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Exceptions-during-registry
this message in context:
http://tapestry.1045711.n5.nabble.com/Exceptions-during-registry-startup-tp2431019p2842239.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
Which version of T5? I had thought that it would report problems at
startup a bit better.
Can you use the debugger to catch the NPE? If so, add an issue with
the stack trace to the NPE and I'll make sure it gets reported better.
On Fri, Apr 24, 2009 at 3:24 AM, Alfie Kirkpatrick
Hi, I am staring at an error in my log:
11:02:22.617 [main] ERROR o.a.t.i.s.T.RegistryStartup - An exception
occurred during startup: java.lang.NullPointerException
While this is undoubtedly the result of some very poor code on my part,
the log doesn't really help me locate it!
Is
