One comment that came up, which I have also thought about as well, is why
Fortress continues to attempt to initialize additional components after one
has failed.
It is due to the async initialization of components. There is a command in the queue to initialize each component, and when one fails, the queue continues to process commands.
That is what it looked like. Any ideas on how I could get the behavior of simply
kicking out a message like "Password attribute not defined" and then have the
application exit fairly gracefully. The message is what is being thrown in the
ConfigurationException that is leading to the chain of failures in dependent
components.
Cheers, Leif
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
