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
wrote:
> Hi, I am staring at an error in my log:
>
>
>
> 11:02:22.617 [main] ERROR o.a.t.i.s.T.RegistryStartup -
My @Startup method does get invoked, and I do see "Error invoking startup
method" in the log file. However, I never get a stack trace, neither in the
log file nor on system out/err. Does this mean I've misconfigured something?
Cheers,
Peter
--
View this message in context:
http://tapestry.10457
On Thu, Sep 16, 2010 at 6:20 AM, Peter Niederwieser wrote:
>
> 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 co
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-st
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
wrote:
> Hi, I
