Leo, > The default implementation, although often (almost always) > built from an XML file, has *no* link to the XML file that > created it. Thus, in the default impl, changes are never > stored.
The don't you need some sort of marker to indicate the config has changed since it has been created. Such as an isDirty() boolean marker to determine if the configuration has changed since it was created from some source what ever that may be. Or is this something that should be left to the implementation to expose? I think this should be put into the interface I think because regardless of the implementation there is a configuration source and if the configuration has changed since it was loaded from this source applications and containers should be able to know of the change. Or even go further there should be some mechanism for registering listeners and notifying those listeners when changes occur. What do you think? The reason why I bring this up is because these are all at the API level which goes into framework. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
