----- Original Message ----- From: "Stephen McConnell" <[EMAIL PROTECTED]>
> Putting something into framework is a lot more to do with the definition > of the Avalon component lifecycle model. It really does not matter if > the intention is to expose this during the lifecycle phases or not - the > thing is that if it goes into framework it becomes part of framework. I think everyone here is conscious of that. > The alternative is to put it into Excalibur Configuration along with the > other configuration additions - such as: > > - CascadingConfiguration > - ConfigurationUtil, > - NamingConfigurationBuilder > - the config merger and split helpers > - and the config validation stuff. Agree. Maybe the proposal of addition of this interface to the framework was a bit anticipated. regards, hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
