Hi Anton, Thanks for the input. I am interested in restarting only the particular block for which the configuration has changed not the whole application. The reason being I would not want my entire services to be down when I am willing to change configuration of a single block. I am expecting if the framework has a way of diff'ing the old and new configuration (config.xml) and notify only the appropriate blocks.
Any inputs on second thought? <Add MBean set interfaces to accept new configurations. User can modify the parameters using mx4j http browser. The problem here is, how can the block save the configuration to config.xml.> Any other ideas/implementations to reload configuration without having to bring down the applications? Thank You Chinmaya -----Original Message----- From: Anton Tagunov [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2003 1:58 AM To: Avalon framework users Subject: Re: Dynamic Blocks Configuration Hello Chinmaya! CS> 1) A phoenix system component can poll for the config.xml changes, CS> if any changes found, make reconfigure (say of Reconfigurable interface) CS> calls to blocks. Not sure if this mechanism exits. Not at all an expert on this (especially no knowledge on Phoenix), but I guess excalibur-monitor package (especially the impl.ActiveMonitor) has somewhat to do with what you need. BTW playing with Fortress inside a servlet I have adopted the following approach: on every request if the time since last check exceeds a certain configurable threshold the validity of the .xconf file is checked. If the file has changed, then a new instance of Fortress is created. If that is a success the prev. instance is decommissioned and the new instance is used. (This might probably run on top of impl.PassiveMonitor or its close relative, however not knowing about that class I used a different custom approach). So you see, you have mentioned config.xml changes. But config.xml controls the complete system. Is restarting the whole system what you want? Also impl.ActiveMonitor might probably restart the whole system not at the next request (as in my case) but periodically polling the config file - AFAIK that's what impl.ActiveMonitor does... - Anton --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
