Robert Burrell Donkin wrote:
On Mon, Sep 15, 2008 at 6:13 PM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Robert Burrell Donkin ha scritto:
2 moving forward, would it be convenient to use an object model to
decouple configuration from avalon?
Maybe our only alternative...
object models can sometimes be useful tools for documenting the
configuration as well
Do you mean a set of classes dedicated to hold only configuration info?
if yes, I'm all for it. +1
I think this is one of the crucial (if not the single most important)
things to do to get away from intrusive containers.
but accessing the current configuration as it is now is very tightly
coupled with business logic. moving away from it changes a lot of code
and would require loads of unit tests.
maybe a dual model could make this work, one that on the one side
behaves like nice and friendly configuration objects with getters and on
the other side like our current tree-like generic configuration a la Avalon.
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
