Yes, that's the badger. If we can hide stuff behind there it means for minimal impact if people want to use a different configuration mechanism. On the surface, I can't see it being that hard - but then I've not read the Groovy code yet to see how that works or thought very deeply about it.
On Tue, Nov 23, 2010 at 11:12 AM, Sim IJskes - QCG <s...@qcg.nl> wrote: > On 11/23/2010 12:06 PM, Tom Hobbs wrote: > >> If we could hide each kind of configuration option (standard config >> files, groovy classes, configuration service, something else) behind >> the same decorator interface, then we can swap configuration options >> without changing any of the service code. >> >> Or have I got the wrong end of the stick? > > No, i guess to are refering to the Configuration interface? :-) > > >
