VMware Communities: Missing item in Plugin Schema question ...

VMware

Up to Discussions in Orchestrator APIs

Sample Code
Tech Exchange

Orchestrator APIs:

This Question is Answered

2 "helpful" answers available (6 pts)

2 Replies Last post: Oct 12, 2009 1:08 PM by Cédric

Missing item in Plugin Schema question posted: Oct 8, 2009 6:23 AM

BlueDevilDan

18 posts since
Jun 17, 2009

In looking at the schema for plugins http://www.vmware.com/support/orchestrator/plugin-4-0.xsd I notice that when defining a scripting object there are descriptions allowed for objects, methods, and constructors, but not attributes. However, when using the Orchestrator UI for building the workflow action scripting, the API search for existing items shows attributes with descriptions (Array.length for example).

So my question is whether descriptions are allowed for attributes in the Orchestrator engine and if this was simply forgetten to be added to the plugin schema?

Tags: plugin, schema

Re: Missing item in Plugin Schema question

1. Oct 9, 2009 9:28 AM

in response to: BlueDevilDan

BlueDevilDan

18 posts since
Jun 17, 2009

Apparently a description for attributes is not accepted in my Orchestrator (which says it is version 3.2.1). From the log file

2009-10-09 12:21:25.745-0400 WARN XmlModuleDescriptionReader Plugin config file 'netapp-vmo-dfm-zapi.dar' : SAX parsing exception 'cvc-complex-type.2.2: Element 'attribute' must have no element children, and the value must be valid.'

That said, being able to provide a description for attributes (and method parameters) so that description can be seen in the API Search GUIs I think is a necessary enhancement to the plugin vso.xml definition.

Re: Missing item in Plugin Schema question

2. Oct 12, 2009 1:08 PM

in response to: BlueDevilDan

Cédric

79 posts since
Jun 27, 2008

In the <object>, use a <attributes> collection and the iterate each <attribute>

Sample:


<scripting-objects>
    <object script-name="MyScriptingObject" ... >
        <attributes>
            <attribute script-name="MyValue" .....>
                 <![CDATA[http://Custom field values.]|http://Custom field values.]]>
            </attribute>
             ...
        </attributes>
    </object>
</scripting-objects>