Provide new runtime bean registrator for recreated module 91/32291/2
authorMaros Marsalek <mmarsale@cisco.com>
Fri, 8 Jan 2016 16:32:06 +0000 (17:32 +0100)
committerGerrit Code Review <gerrit@opendaylight.org>
Fri, 8 Jan 2016 20:17:56 +0000 (20:17 +0000)
commit37cbf86dd56fb1d79a817750951283e1ae688cf7
treed5ea0083f54952ae93647cd7fdcc6147223c9259
parentcabb96a79c2b155092e65fb25d271fff85c3f786
Provide new runtime bean registrator for recreated module

After recent changes in config-manager, runtime bean registrations are not
preserved after reconfiguration of a module. This is caused because internal
jmx registrators are now properly closed. Runtime bean registrations relied
on previous, incorrect behavior.

This commit fixes the issue by recreating runtime bean registrator for each module.
However there's a possible leak if clients do not close runtime bean registrations
in their createInstance methods.

Change-Id: I37f0956effdd2a183390252615c23a90e23ebe8e
Signed-off-by: Maros Marsalek <mmarsale@cisco.com>
opendaylight/config/config-manager/src/main/java/org/opendaylight/controller/config/manager/impl/ConfigRegistryImpl.java