I just added a Persistable interface so that Components that may change their configuration parameters during run-time will be able to save those changes to the configuration file. Here is where it will really help:
ExcaliburComponentManager/Selector classes can be modified to be persistable, and perform self-tuning. In other words, the magic parameters for pool sizes on Poolable Components can be altered to what the last maximum number of concurrent components in the pool were. It can also calculate the most efficient grow size and minimum components by an algorithm. With that done, the persistable interface will automagically plant those attributes as it gives returns its Configuration object. It also allows for self-healing configuration files so that as a deprecated Configuration parameter is read in and handled, the current prefered parameters are persisted. I came up with this approach due to both the dialogue with the dbXML folks, and the way that Axis needs to handle persistance. Axis can add new Handlers, etc. during the normal life cycle, and we need to reflect that in the Configuration. Persistable extends Configurable, and has only one method, "persist()" that returns a Configuration object. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
