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]
