HTML Client SDK FlingOverviewandReleaseNotes
HTML Client SDK FlingOverviewandReleaseNotes
SDK tools to help you develop and build user interface extensions which are compatible with both
vSphere Client (HTML5) and vSphere Web Client. The HTML Client SDK Fling is based on the existing
HTML Bridge APIs which allows already existing HTML Bridge plug-ins functionality to be fully
supported in the new vSphere Client (HTML5). You can use the HTML Client SDK Fling to extend
existing HTML Bridge plug-ins or build pure HTML5 plug-ins from scratch and test them in the vSphere
Client (HTML5).
You can successfully deploy existing or new HTML plug-ins on the vSphere HTML5 Client Fling if you
have followed the forward compatibility instructions for developing HTML-based plug-ins.
The following features have been introduced to the HTML Client SDK Fling:
HTML-Based Portlet Support on Summary View
Starting with the first HTML Client SDK Fling release, plug-in developers can implement HTML-based
portlets and display them within an existing Summary view for vSphere or custom object.
HTML-Based Plug-Ins Compatibility
To ensure that your HTML-based plug-ins are compatible with the new HTML5-based vSphere Client
(in addition to the already existing vSphere Web Client), always use relative URLs in your HTML and JS
code and use the webContextPath defined in web-platform.js file.
For detailed technical instructions refer to the documentation provided inside the SDK and updated
samples.
Note: This is a Fling release and the official documentation is not completed. Please use the
documentation provided inside the SDK and feel free to share your feedback.
RELEASE NOTES
Use the latest version of Getting_Started_with_HTML_Client_SDK_Fling.pdf after you
download a new Fling version. All new features are covered.
When an action controller returns a successful result the client now broadcasts a global
refresh event to give the plug-in a chance to update its view (as long as it is using the
setGlobalRefreshHandler API). For instance the Summary view in ChassisA or
Chassis B samples is updated correctly after you edit a chassis.
Bug Fixes
Global View size is adjusted correctly and does not spill out.
Saving settings in Global App sample under Windows is fixed (method
getGlobalViewDataFolder() is unified throughout all the OS).
Additional Notes
You no longer need to download the entire Adobe Flex SDK to build string resources like swf
files. Flex compiler is available from \html-client-sdk\resources\flex_sdk_4.6.0.23201_vmw
folder.
We have done plenty of updates to the documentation! Have a look at the /docs directory.
Bug Fixes
The Administration category and VM Configure tab can now be extended so plug-ins can add
their own views at these locations.
Fixed the navigation to a custom object view after clicking on that object in a list view.
Fixed the MANIFEST and plugin-package.xml of plugins generated with the scripts in
html-client-sdk/tools/Plugin generation scripts/ so that they can be deployed correctly.
Fixed a nullPointerException in vsphere-wssdk samples DataProviderImpl.java (when a host
didnt have any VM)
Additional Notes
Adding dataservice.vmodl.version=public in webclient.properties is no longer
necessary when running with vCenter Server 6.5
In Eclipse, the vSphere SDK Tools menu was removed because it didnt work and it was already
replaced by the command line script under html-client-sdk/tools/Plugin generation scripts/
Bug Fixes
sendNavigationRequest API is fixed to update the left-hand side navigator.
It is possible to add views under VM > Configure, i.e. extend
vsphere.core.vm.manageViews
vCenter Server registration failure is fixed and the previous issue: An error occurred while
sending an authentication request to the vCenter Single Sign-On server - An error occurred
when processing the metadata during vCenter Single Sign-On setup - Keystore to be used for
remote connections is null.. no longer appears.
HTML SDK Fling 3 [Aug 30, 2016] - Build 4321818
New Features
If you want to register a plug-in as a vCenter server extension, you can use the newly
introduced
tool available from "html-client-sdk\tools\vCenter Plugin Registration" directory. In addition
to prebuilt extension-registration.sh for Mac OS and extension-registration.bat for Windows
OS scripts, this directory contains a plug-in registration source code that can be customized to
fit your own business purpose.
OSGi usage validation is present in this version of HTML Client which helps you identify if your
plug-in follows important rules outlined in the "OSGi-Specific Recommendations" section of
the Best practices guide.
Bug Fixes
Ant build scripts of SDK samples report SUCCESS even when the compilation fails.
Persistent XSS in VM name when navigating to a VM is fixed.
Fixed the loading of string resources for plugins deployed as vCenter extensions.
Bug Fixes
Missing extension vsphere.core.navigator.solutionsCategory is now added.
Composed exception in vsphere-wssdk summary sample, when portlet viewed the first time,
is fixed.