Alex,
then we are talking about a third interface. See:
Configuration: A configuration that *you* can't change,
and that *doesn't* change.
MutableConfiguration: A configuration that *you* can
change. (And that changes, because of that.)
What you want is something like "DynamicConfiguration":
A configuration that *you* can't change, but that the container *can*
and presumably *will* change.
The question is whether this should be done via listeners, or whether
we should just pass the ConfigurationChangeEvents directly to the
component. I.e.
1. Configuration changes.
2. Listener gets notified.
3. Component inspects the listener parameters to find out what
changed.
4. Component extracts the new value from the configuration.
5. Component reconfigures itself.
Or:
1. Configuration changes.
2. Component receives an Event with key + value of configuration
element that changed.
3. Component reconfigures itself.
/LS
> From: Alex Karasulu [mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
