Denis_Chorbadzh's Posts

Re: Global refresh handler not called after action in 6.5U1 (regression from 6.5.0d/5097204)

by VMware Employee in vSphere Client SDK Discussions
‎08-08-2017 03:33 AM
‎08-08-2017 03:33 AM
Yes, the API setGlobalRefreshHandler() works. It can be seen in our chassisA/chassisB SDK samples.

Re: Global refresh handler not called after action in 6.5U1 (regression from 6.5.0d/5097204)

by VMware Employee in vSphere Client SDK Discussions
‎08-07-2017 11:36 PM
‎08-07-2017 11:36 PM
Hi Chris, Yes, this is a known issue. In fact, there were serious performance considerations for automatically calling the Global Refresh after each plugin change event and we have decided to re... See more...
Hi Chris, Yes, this is a known issue. In fact, there were serious performance considerations for automatically calling the Global Refresh after each plugin change event and we have decided to remove it for the time being. We are working on providing a better way for plugins to refresh their data but, for now, the workaround is to call the Global Refresh manually.   Regards, Denis

Re: SSL problems

by VMware Employee in vSphere Client SDK Discussions
‎06-27-2017 03:12 AM
‎06-27-2017 03:12 AM
Hi,   Since you are making rest calls to your back end server, the issue is most probably not related to the vSphere but to your server certificate configurations. You may try to fix the probl... See more...
Hi,   Since you are making rest calls to your back end server, the issue is most probably not related to the vSphere but to your server certificate configurations. You may try to fix the problem using the steps provided here: https://confluence.atlassian.com/kb/unable-to-connect-to-ssl-services-due-to-pkix-path-building-failed-779355358.html   Denis

Re: Stale Privileges

by VMware Employee in vSphere Client SDK Discussions
‎06-27-2017 01:54 AM
‎06-27-2017 01:54 AM
Hi,   I would suggest that you restart the server after unregistering your plugin. This should clean the remainings.   Denis

Stability fix for ProviderAdapters

by VMware Employee in vSphere Client SDK Discussions
‎03-10-2017 07:50 AM
‎03-10-2017 07:50 AM
Hi all, If you are using a “PropertyProviderAdapter” or a “DataProviderAdapter” and you register the adapter with the DataService registry on creation, make sure that you unregister the adapter... See more...
Hi all, If you are using a “PropertyProviderAdapter” or a “DataProviderAdapter” and you register the adapter with the DataService registry on creation, make sure that you unregister the adapter on destruction. This should be done in order to prevent a possible memory leak. For example: Unregister: public void destroy() { _serviceExtensionRegistry.unregisterDataAdapter(this); } In addition, make sure that you include “destroy-method” attribute in the bean’s definition.                 <bean name="DataProviderImpl"                             class="com.vmware.samples.vspherewssdk.DataProviderImpl"                             destroy-method="destroy"> Currently, the issue is reproducible in the WSSDK sample plugin and will be addressed in a future Fling release. Note: This is a stability improvement, although the case is not currently reproducible in a production environment. Regards, Denis