Torsten:
I'm having trouble building a test case for the cascading configs
using DefaultConfiguration and AbstractConfiguration based on the
diffs. The issue concerns the point at which a configuration
instance is created.
Here are the two use cases that I envisage - both concern the
creation of a new configuration that is bound to an existing
parent configuration.
1. when creating a cascading configuration from a file or
stream using DefaultConfigurationBuilder, e.g.:
builder.build( my_stream, defaultConfig );
2. when creating a cascading configuration from a
configuration child
config.getChild( "profile", defaultConfig );
Neither of the above cases are supported by the proposed change.
The approach taken in CasacadingConfiguration deals with these
cases through a target/parent wrapper approach. However, the
attribute resolution mechanism in the updated AbstracConfiguration
is much more elegant - but I haven't got my head around an
appropriate resolution. Any thoughts ?
Cheers, Steve.
> -----Original Message-----
> From: Torsten Curdt [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, 13 February, 2002 11:33
> To: Avalon Developers List
> Subject: [PATCH] Re: Cascading Configuration
>
>
> Here we go...
> ...it would be great if someone could look over this
> and then apply it. I changed the AbstractConfiguration
> and DefaultConfiguration as discussed before
>
> cheers
> --
> Torsten
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
