VMware
Orchestrator APIs:

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
1 Replies Last post: Sep 30, 2009 12:06 AM by Cédric  

Better documentation for plugin XML structure posted: Sep 28, 2009 7:57 AM

Click to view BlueDevilDan's profile Novice
BlueDevilDan
18 posts since
Jun 17, 2009

I have been looking at a the XML Schema definition for Orchestrator plugins (http://www.vmware.com/support/orchestrator/plugin-4-0.xsd). While this helps me to see all the possible elements and attributes, it does not really provide much explanation for them.

For example, in the definition for a scripting object attribute is an XML attribute called returnType which is if type string. However, there is no defined XSD enums or other comment for what the valid values are for this string. Is it Java types? Is it some other keyword mechanism to support the JavaScript/Java mapping?. The plugin developer's guide does not provide this.

I have the basic pattern for plugin development understood and working. What I' looking for is a more complete reference information for all the details. It would be fine for me for this to be annotated in this plugin schema. In fact that is probably the correct place. So, that is my suggestion. In the mean time, is there a resource that I have not yet found that can provide me with this detail?


Re: Better documentation for plugin XML structure

1. Sep 30, 2009 12:06 AM in response to: BlueDevilDan
Click to view Cédric's profile Hot Shot
Cédric
75 posts since
Jun 27, 2008
Hi,

The result type is one of your scripting objects type or base type. It's here "only" for documentation (when the scripting documentation is auto generated for each plug-in)

Actions

Developer SDKs & APIs

Developer Resources

Developer Social Media

Communities