Stop components when config timestamp changes.
Review Request #4464 - Created March 23, 2012 and submitted
Added functionality to support stopping of components if configuration changes.
Tested change of configuration - no bind exception when port remains the same. When port changes, old port is no longer accessible, new port is.
Posted (March 23, 2012, 6:55 a.m.)
Thanks for the patch Hari. A couple of suggestions to consider: * Rather than adding another method in NodeConfigurationAware which is invoked by the PropertiesFIleConfigurationProvider - it will be better to instead keep a track of the old configuration within the DefaultLogicalNodeManager which onNodeConfigurationChanged() invocation first shuts down and removes the old components from last configuration before initializing the new configuration based components. * Similarly, rather than introducing setStopStateImmediately(), we should instead fix the implementation of unsupervise() to do the necessary shutdown and cleanup.