BlueDevilDan
Contributor
Contributor

Missing item in Plugin Schema question

Jump to solution

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 (2)
0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal

In the

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>

View solution in original post

0 Kudos
2 Replies
BlueDevilDan
Contributor
Contributor

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 Plugin config file 'netapp-vmo-dfm-zapi.dar' : SAX parsing exception 'cvc-complex-type.2.2: Element 'attribute' must have no element , 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.

0 Kudos
admin
Immortal
Immortal

In the

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>

0 Kudos