We have encountered an issue with installing, uninstalling and reinstalling our plugin.
It appears that when we do an uninstall of our plugin, our components are still left active in the vCenter Web Client service. We find that when we reinstall our plugin, the old components are used. They are singletons that were started up and they load information from the MOB plugin registration to determine were our server URL and other information is at. If we first install our plugin server on one system, uninstall it, and then reinstall it on another system our bean components haven't been stopped and are still using the URLs for the old install. These are the beans that are defined in the bundle-context.xml file located in the META-INF/spring directory.
Is there a mechanism that we should be using to have the web client server stop and unload these running components? Or is this something we need to account for and come up with our own mechanism to kill off our pieces when our plugin is uninstalled.
↧
Uninstall and unloading of bundle context beans
↧