Extension Templates in the vSphere Web Client SDK contains the Extension Templates included with the vSphere Web Client SDK.
|
|
|
You must supply a namespace and an objectType for the objectViewTemplate. A best practice is to use reverse domain naming, such as com.myCompany, to start the namespace name, followed by a unique extension name. For example, if your company name is Acme, and you create a plug-in for a custom object called a Rack, you could use the namespace com.acme.plugin01.rack.
The objectViewTemplate creates extension points in the format namespace.extension-point-name. To continue the previous example, one extension point might be com.acme.plugin01.rack.monitorViews.
|
|
Creates a standard Summary tab with an optional header at the top, and a main area that can contain one or more Portlet data views.
You must supply a namespace, and can optionally supply a summaryHeaderView, for the summaryViewTemplate. You must create an instance of the objectViewTemplate before creating a summaryViewTemplate instance.
The summaryViewTemplate creates the extension point namespace.summarySectionViews. When you create data view extensions at this extension point, they data views appear as Portlets in the Summary tab.
|
|
namespace: a unique identifier used to avoid name clashes with other extensions
title: the custom object text label
icon: the custom object icon resource
objectType: the vSphere type name for the custom object
listViewId: the data view that appears when the user clicks the collection node, usually an object list
parentUid: the object collection node’s parent node in the object navigator control
|