What do people think about moving the class CascadingConfiguration from cornerstone/apps/orb to avalon/framework/configuration?
The class is basically an implementation of Configuration that takes a primary and default configuration as constructor arguments. Resolution of attribute values and child elements are resolved against the primary configuration - and if that fails, the implementation attempt to resolve the request against the secondary default configuration (which could be another CascadingConfiguration). Resolution of children for a particular "name" result in the aggregation of the primary and default configuration child elements. Thoughts ? Cheers, Steve. --------------------------------------------------------- Stephen McConnell wrote: > I think it [CascadingConfiguration] would make a good > addition to the framework/configuration package as it not > dependent on any other packages. Torsten Curdt wrote: > Cool... Since I'm no avalon committer - could you do it then, please? > Let me know if I can help... Shawn Boyce wrote: > I agree. It looks useful and I can make use of it in my service. > It can replace some existing code that does basically the same thing. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
