Torsten:
The only reason I didn't do that is that I didn't want to mess with the existing Configuration class. If cascading behaviour was introduced into DefaultConfiguration, then yes, you could do this. If cascading semantics are supplementary then you end up with the constructor that takes the base and parent configuration. Cheers, Steve. > -----Original Message----- > From: Torsten Curdt [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, 12 February, 2002 13:10 > To: [EMAIL PROTECTED] > Subject: Cascading Configuration > > > Wouldn't it make sense to also have a > > class CascadingConfiguration extends AbstractConfiguration { > > public CascadingConfiguration( Configuration conf ) { > ... > > So we can apply the same pattern as for the ComponentManager or the > RoleManager? So you easily split configuration files... > -- > Torsten > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
