We started to build some parts of our plugin in HTML and noticed that in vcenter version 6.0.0.2559267, the flex part of our plugin deploys fine, but the HTML views show this error. It works fine on versions 6.0 U1 and above, but not on this particular build. Was HTML supported on this version of vcenter?
Error: Unsupported plugin dependency type css
at com.vmware.extensionfw::PluginModuleLoader/loadDependency()
at com.vmware.extensionfw::PluginModuleLoader/loadModule()
at com.vmware.extensionfw::PluginClassLoader/onPluginInfoRetrieved()
at com.vmware.extensionfw::PluginClassLoader/instantiate()
at WorkItem_LoadingType()
at com.vmware.flexutil::MxmlDeserializer/xmlToObjectInternal()
at com.vmware.flexutil::MxmlDeserializer/processWorkItems()
at com.vmware.flexutil::PseudoThread/onTimer()
at com.vmware.flexutil::PseudoThread/start()
at com.vmware.flexutil::MxmlDeserializer/xmlToObjectAsync()
at com.vmware.extensionfw::ExtensionObjectParser/parse()
at com.vmware.extensionfw::ExtensionObjectFactory/getObject()
at com.vmware.extensionfw::ExtensionManager/createObjectInternal()
at com.vmware.extensionfw::ExtensionManager/onResourceModulesLoaded()
at com.vmware.extensionfw::MiscUtil$/loadResourceModules()
at com.vmware.extensionfw::ExtensionManager/createObject()
at com.vmware.vsphere.client.views.app::AppViewMediator/showDomainView()
at com.vmware.vsphere.client.views.app::AppViewMediator/activateExtension()
at com.vmware.ui.navigation::NavigationManager/onExtensionHostsRetrieved()
at com.vmware.extensionfw::CallbackUtil$/callback()
at com.vmware.extensionfw::ExtensionManager/getExtensionHosts()
at com.vmware.ui.navigation::NavigationManager/onNavigationRequest()
at com.vmware.vsphere.client.views.app::AppViewMediator/onObjectNavigatorNodeSelected()
at flash.events::EventDispatcher/dispatchEvent()
at mx.core::UIComponent/dispatchEvent()
at com.vmware.ui.objectnavigator::ObjectNavigator/onNodeSelected()
at flash.events::EventDispatcher/dispatchEvent()
at mx.core::UIComponent/dispatchEvent()
at com.vmware.ui.objectnavigator.views::CategoryNodeViewMediator/handleNodeSelection()
at com.vmware.ui.objectnavigator.views::CategoryNodeViewMediator/onNodeSelected()
at flash.events::EventDispatcher/dispatchEvent()
at mx.core::UIComponent/dispatchEvent()
at com.vmware.ui.objectnavigator.views::CategoryNodeListView/nodeSelectionOrFocusChanged()
at com.vmware.ui.objectnavigator.views::CategoryNodeListView/__listView_selectionChanged()
at flash.events::EventDispatcher/dispatchEvent()
at mx.core::UIComponent/dispatchEvent()
at com.vmware.widgets.controls.navigatorclasses::TreeNodeView/onNodeSelected()
at flash.events::EventDispatcher/dispatchEvent()
at mx.core::UIComponent/dispatchEvent()
at com.vmware.widgets.controls.navigatorclasses::TreeNodeItem/setSelectedState()
at com.vmware.widgets.controls.navigatorclasses::TreeNodeItem/setNodeSelected()
at com.vmware.widgets.controls.navigatorclasses::TreeNodeItem/onItemClicked()
Thanks,
Virat
> in vcenter version 6.0.0.2559267
Can you provide the version number for Web Client in the About vSphere Client dialog box?
It looks like you're talking about 6.0 GA from 2015.
HTML views have been supported since Web Client 5.5.1 using the "HTML bridge". Your error "Unsupported plugin dependency type css" seems to be related to a <dependency type="css" ...> in plugin.xml: do you have one and what happens if you try the 6.0 Client after removing it?
Hi Laurent,
The vSphere Web Client version is Version 6.0.0 Build 5318172.
It looks like you're talking about 6.0 GA from 2015.
Yes.
As for the type="css" part, if I remove it, the html components of my plugin disappear completely from all versions (even 6.5). Is there another workaround?
Virat
Please send your plugin.xml because I don't understand what your "css" dependency is about.
If you look at the vsphere-wssdk sample, which is also a hybrid flex+html plugin, the dependency looks like this:
<dependencies>
<dependency type="css" uri="vspherewssdk/assets/css/plugin-icons.css" />
</dependencies>
I would be interested to see if that sample works in your 6.0 setup. Can you add a plugin-icon.css file to that sample and reproduce the problem?
Hi Laurent,
I have been trying to get my plugin to work with 5.5U1 as well and noticed that the <dependencies>...</dependencies> part is not mentioned in the documentation until 6.5 in the "Handling icons outside the HTML view". Also, my plugin is not a full hybrid, I have one war that has all the HTML5 components and another war that has the flex components. The html war is the one that fails to deploy because of the <dependencies /> part of the plugin.xml, if I remove them I got the error below when I try to open the html view
Error: Class not found 'useHtmlContentImage' while loading plugin id com.nimblestorage.hi.client.nimblestorageclient
at com.vmware.extensionfw::PluginClassLoader/onPluginInfoRetrieved()
at com.vmware.extensionfw::PluginClassLoader/instantiate()
at WorkItem_LoadingType()
at com.vmware.flexutil::MxmlDeserializer/xmlToObjectInternal()
at com.vmware.flexutil::MxmlDeserializer/processWorkItems()
at com.vmware.flexutil::PseudoThread/onTimer()
at com.vmware.flexutil::PseudoThread/start()
at com.vmware.flexutil::MxmlDeserializer/xmlToObjectAsync()
at com.vmware.extensionfw::ExtensionObjectParser/parse()
at com.vmware.extensionfw::ExtensionObjectFactory/getObject()
at com.vmware.extensionfw::ExtensionManager/createObjectInternal()
at com.vmware.extensionfw::ExtensionManager/onResourceModulesLoaded()
at com.vmware.extensionfw::MiscUtil$/loadResourceModules()
at com.vmware.extensionfw::ExtensionManager/createObject()
at com.vmware.vsphere.client.views.app::AppViewMediator/showDomainView()
at com.vmware.vsphere.client.views.app::AppViewMediator/activateExtension()
at com.vmware.ui.navigation::NavigationManager/onExtensionHostsRetrieved()
at com.vmware.extensionfw::CallbackUtil$/callback()
at com.vmware.extensionfw::ExtensionManager/onExtensionHostsReturn()
at com.vmware.extensionfw::CallbackUtil$/callback()
at com.vmware.extensionfw::ExtensionServiceProxy/notify()
at com.vmware.flexutil.proxies::BaseProxy/result()
at com.vmware.flexutil.proxies::BaseProxy/onInvocationComplete()
at OperationInvoker/resultResponseForRequest()
at OperationInvoker/result()
at mx.rpc::AsyncToken/http://www.adobe.com/2006/flex/mx/internal::applyResult()
at mx.rpc.events::ResultEvent/http://www.adobe.com/2006/flex/mx/internal::callTokenResponders()
at mx.rpc::AbstractOperation/http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()
at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::resultHandler()
at mx.rpc::Responder/result()
at mx.rpc::AsyncRequest/acknowledge()
at NetConnectionMessageResponder/resultHandler()
at mx.messaging::MessageResponder/result()
Hi Virat,
Please check if there is no conflict between your two wars - e.g. remove the flex one and see if you get the same error.
Could you please provide a code snippet of the relevant part of your original plugin.xml so that I can have a look?
As Laurent suggested, are you able to reproduce it with the wssdk sample on the same environment?
Cheers,
Vladi
Hi Laurentsd,
I am also facing the similar issue but I am getting the dependency error in Flex client, in HTML5 Client the Summary Portlet is coming fine.
So I added a dummy plugin-icons.css file in '/assets/css' folder and un-commented following from plugin.xml file:
<dependencies>
<dependency type="css" uri="vspherewssdk/assets/css/plugin-icons.css" />
</dependencies>
built and installed vspherewssdk sample plugin deployed it in vCenter server and realized that I am getting the same error in flex part - http://prntscr.com/g5xzbt
Whereas in HTML5 Client the UI is coming properly - http://prntscr.com/g5xvzv
I am attaching the vsphere-wssdk-sample.zip (package file)
Next when I commented the dependencies part in plugin.xml file and deploy, the Flex Portlet and HTML Portlet are coming fine without any errors.
But unfortunately the external icons are not getting displayed if dependency part is commented out.
HTML SDK - v6.5.0.10000-5972228
Web Client - v6.5.0.10000-5973321
This seems to be a problem with hybrid plugins, when the plugin.xml combines both Flex and HTML views. The only work-around I can think of is to split your plugin into 2 wars (with different plugin ids in plugin.xml and Web-ContextPath in MANIFEST.MF):
- one war only has Flex views and includes an attribute moduleUri="myplugin.swf" in plugin.xm, but no css dependency.
- the other war only has HTML views, doesn't have any moduleUri attribute but a css dependency in plugin.xml
That worked. Thank you...