-----Original Message----- From: Leo Sutic [mailto:[EMAIL PROTECTED]
So I'd like to have an interface - MutableConfiguration that will extend Configuration, but add the mutators from DefaultConfiguration - setAttribute, addChild, etc. DefaultConfiguration would then implement this interface.
What do you think?
I think I'm following you but I'm interested in better understanding the use case. What types of components would be messing with their configuration? What would have access to a MutableConfiguration object?
The easy answer to that question comes into play with components that want to save their run-time state so that the next time the system is brought back up, they can be fully restored.
One such example would be the Axis system (it is not based on Avalon at this time). As web services are added to the system at runtime through its runtime interface, it needs to modify the configuration so that it knows to start up the new web service at runtime.
Granted, this *might* be addressed by providing a work space to save these config files. At the same time, it would be much simpler to store the configuration where the rest of the configuration information is stored. The only entity that knows that information is the container. That would require and interface between the container and the component to be able to change the config info and persist it between sessions.
This subject has been discussed in the past, although I can't venture to give a timeframe. You might want to search marc.theaimsgroup.com to find past discussions and proposals on the subject.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
