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?
The required true/false can be determined if we keep track of optional dependencies.
IOW all components are considered optional unless they are referenced as required (the current default).
-- "You know the world is going crazy when the best rapper is a white guy, the best golfer is a black guy, The Swiss hold the America's Cup, France is accusing the US of arrogance, and Germany doesn't want to go to war. And the 3 most powerful men in America are named 'Bush', 'Dick', and 'Colon' (sic)".
-----Chris Rock
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
