If I remember correctly failed life cycles of context elements are not propagated to the life cycle of the context itself (like failed contexts are not propagated to the life cycle of the server itself). Check the life cycle of the SecurityHandler ServletHandler and SessionHandler of the context, too.
If I remember correctly failed life cycles of context elements are not propagated to the life cycle of the context itself (like failed contexts are not propagated to the life cycle of the server itself). Check the life cycle of the SecurityHandler, ServletHandler and SessionHandler of the context, too.
I've tried attaching listeners to all of those with no luck. I'm looking at the source for WebAppContext. This Log.
Warn matches the log message I'm seeing (except I see it at Error level...). If I'm reading this right, the error is completely swallowed. The relevant part in AbstractLifeCycle sets failures when exceptions are thrown in the subclass doStart().
– Patrick Dec 1 '10 at 22:57 I guess I'll try extending WebAppContext to be more throwy with exceptions. – Patrick Dec 1 '10 at 23:00 That worked more or less. See my posted answer.
Thanks for your hints. – Patrick Dec 1 '10 at 23:12.
As per my comments to Heri's answer, WebAppContext swallows exceptions. They would otherwise be caught by AbstractLifeCycle and failure events sent out. This gets me most of the way there: public class ThrowyWebAppContext extends WebAppContext { @Override protected void doStart() throws Exception { super.doStart(); if (getUnavailableException()!
= null) { throw (Exception) getUnavailableException(); } } }.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.