Torsten Curdt wrote:
> 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
? How do you see this working?
Seriously, the Configuration works fairly elegantly right now. If I
have a child that uses a Configuration block, I send the child to it.
That Child Component cannot see any configurations from the parent.
A Configuration != Manager, so I don't see how the cascading properties
will solve any real needs.
There is something else that I want to work towards (but am not anywhere
near ready yet), which is a ConfigurationManager--i.e. a repository for
Configuration objects for the different types of components. That way,
there can be two-way communication to allow a Component to rewrite its
configuration, and the ConfigurationManager will persist the change.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
