Thanks, Leo! Now I've got how it's going to work. Heterogenous tree. Not bad. If we only had createChild() and no addChild() it wouldn't be possible to mix two configurations into one w/o deep copy.
I'm starging to like this :-) LSU> 1. To add a MutableConfiguration interface LSU> to the framework. The interface itself can be seen at: LSU> http://cvs.apache.org/viewcvs.cgi/avalon/framework/api/src/java/org/apac LSU> he/avalon/framework/configuration/Attic/MutableConfiguration.java?rev=1. LSU> 2&hideattic=0&view=markup +1 provided that immediately after we'll discuss * changes to MutableConfiguration: - getMutableChild( String name ) + /** + * NO autocreate, not appropriate for + * index semantics + */ + getMutableChild( int index ) + isReadOnly() * changes to Configuration: + getChild( int index ) * is add( int index, Configuration conf ) missing? LSU> 2. The second question is where the interface MutableConfiguration LSU> should be. The alternatives are: LSU> + avalon-framework-spi LSU> + avalon-framework-impl I've changed my mind +0 Cheers, Anton --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
