On Thu, 2004-01-22 at 14:52, Leo Simons wrote: <snip> > (the main concern I have is in fact that Joe User may think that > components modifying their own config is a good idea in general; and I > don't think that's the case) </snip>
Joe User here ;-) When you have the management capabilities that exist through JMX interfaces in Phoenix, or whatever instrumentation equivalent exists in Merlin, you end up with components that can get reconfigured on the fly through their management interface. To avoid losing that configuration, it has to be persisted somehow, and this Persistable interface seems much cleaner than how I've ended up solving the same problem in the past (which was basically creating my own DefaultConfiguration, and serializing it in the block home using the DefaultConfigurationSerializer, and reading it back on a call to configure). To me its not so much about the component modifying its config as it is about the config being modifiable through the components management interfaces. Regards, -Cameron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
