Leo, > From: "Leo Sutic" <[EMAIL PROTECTED]> > We agree on this: > > 1. The MutableConfiguration interface is passed from container to > component. +1
> 2. The component accesses the MutableConfiguration interface, and > doesn't know what the real impl class is. +1 > 3. The container know the impl class of the MutableConfiguration being > passed to the component. +1 > 4. The only actor changing the configuration is the component. -1 The container can change the configuration as well. Again if the component is Reconfigurable the container may allow alterations to the components configuration by outside forces like users on a JMX UI for the application inside the container. It only makes sense to have change notification. I respectfully disagree with this statement but perhaps other have their own ideas here and can shed more light one direction or another. > Due to (1), (3), the container can add listeners or whatever, > irrespective > of the functionality exposed by the MutableConfiguration interface. > > The only reason for having listeners in the interface (2) would be so > the component can know when it itself has made a change, after all, > nobody else is making any changes (4). You cannot presume #4 so this is a false presumption. > So just what is your use case for these listeners? The container can make changes on behalf of external agents and the component must be notified of these changes when they occur. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
