Looking at my stack traces. I was noticing that what you are talking about with the CommandManager and a CommandFailureHandler is what happens when when the components are configured to be initialized in the "background".
I have been using "inline" to make sure that all of my components are initialized on startup. Looking at the initialize method of AbstractContainer, it does not look like the CommandManager is even used as the handlers are prepared inline.
That said however, The reason that I have been using the inline initialization
was because any inline components which fail to initialize will cause the
container as a whole to also fail. This was letting me shutdown the
application.
With the CommandFailureHandler, I think I would be able to switch back to using "background" initialization and then shutdown the application from within the handleCommandFailure method as needed.
However. It seems that everyone agrees that a defined component which
fails to initialize should cause the container to fail to initialize. Should we
also modify the AbstractContainer.initialize method so that it fails
immediately rather than building up a list of failures in a "buffer" as is
currently being done? The behavior could be controlled by maybe adding
an optional "required='true/false'" to component declarations?
Well the CommandFailureHandler can also be used for container itself...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
