Stefano Bagnara wrote: > > > Noel J. Bergman wrote: > > Steve, > > > > I suspect that we agree, but I want to confirm. > Configuration should, essentially, be JMX native, and the > configuration scheme should be bridging between the > configuration store and the internal calls. > > > > --- Noel > > Is there any project (better if it's an Apache project) using > this approach? > I would like to put my hands in similar code using this approach...
I'm sure I could trawl up a set of OSS examples that use each aspect of this approach. I'm not sure I could find one which is an exemplar of all aspects acting in unison. I think the only vaguely original things here are that we are delegating to each component the responsibility for how and if it responds to a configuration change and making the original static configuration just the first of many possible dynamic change events. I guess you are asking because there is something you feel unclear or uncomfortable about? If the former I can knock up a UML diagram or two if it would help. If the latter, shout! Cheers -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
