In the process of development I have found that if deploy our plugin on our vcenter server, I cannot then run properly from my Eclipse environment without first unregistering our plugin on our vcenter server. Our eclipse development environments are setup to use that particular vcenter server. From looking in the virgo log of in our development environment I see that the pluging installation on the vcenter server collides with running our plugin in the eclipse development environment with the message: + Context path '/vsphere-client/myPlugin-ui' already exists+. If I unregister our plugin from our vcenter server, then I am able to run just fine using the development eclipse environment.
Another issue I have noticed is when our plugin is installed, we use a different plugin registration key when we register the plugin and what we have in the plugin-package.xml:
+ Plugin id mismatch between the registered extension key (com.companyName.productLine.vmware.vcenter.plugin)+
+ and the id specified in plugin-package.xml (com.ni.productline.vcenterWebClientui). The registration id will be used but you should keep them in sync.+
Our registration key will vary based on the nature of our installation and is set during our final build process. This issue doesn't seem to interfere with the functionality of our plugin, since the system makes the correct choice as to what to use. But it would be nice not have this issue rise in the first place and be present in the log, which could cause some confusion for our customers if they happen to look there. I believe the plugin-package.xml id is set by the line:
plugin id="com.ni.productline.vcenterWebClientui.vcenterwebclientui"
My question is if any of these things can some how be remapped when things are deployed or if there are any other work arounds to avoid these issues?
