Namespace: |
|
Content: |
complex, 6 elements |
Defined: |
globally in common-1.xsd; see XML source |
Includes: |
definitions of 6 elements |
Used: |
at 1 location |
XML Representation Summary |
|||||
<...> | |||||
|
|||||
</...> |
<xsd:complexType name="ScriptType"> <xsd:annotation> <xsd:documentation> Specifies how and when a script is executed during provisioning. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:annotation> <xsd:documentation> Defines a set of operations for which the script should be executed. If more than one operation is specified, the same script should be executed for each of them. If no operation is specified, the script will not be executed (this is meant as poor man's disable feature) </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Defines the order in which a script is executed. (before or after an operation). </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Defines where the script should be executed (connector or resource). If no type is specified, it defaults to resource. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Specifies the language of the script. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Script aguments. The arguments will passed to the script in any way suitable for the script. The argument name is "local" to the script (script-specific). Script name must be unique in the argument set. The order of arguments is not significant. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Script code represented as string. The interpretation depends on script language. If XML elements are used inside, they should be properly escaped. (e.g. using CDATA). </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> |
Type: |
tns:ScriptArgumentType, complex content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="argument" type="tns:ScriptArgumentType"> <xsd:annotation> <xsd:documentation> Script aguments. The arguments will passed to the script in any way suitable for the script. The argument name is "local" to the script (script-specific). Script name must be unique in the argument set. The order of arguments is not significant. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
xsd:string, simple content |
Defined: |
<xsd:element name="code" type="xsd:string"> <xsd:annotation> <xsd:documentation> Script code represented as string. The interpretation depends on script language. If XML elements are used inside, they should be properly escaped. (e.g. using CDATA). </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
tns:ScriptHostType, simple content |
Default: |
"resource" |
Defined: |
<xsd:element default="resource" minOccurs="0" name="host" type="tns:ScriptHostType"> <xsd:annotation> <xsd:documentation> Defines where the script should be executed (connector or resource). If no type is specified, it defaults to resource. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
xsd:anyURI, simple content |
Defined: |
<xsd:element name="language" type="xsd:anyURI"> <xsd:annotation> <xsd:documentation> Specifies the language of the script. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
tns:OperationTypeType, simple content |
Defined: |
<xsd:element maxOccurs="unbounded" minOccurs="0" name="operation" type="tns:OperationTypeType"> <xsd:annotation> <xsd:documentation> Defines a set of operations for which the script should be executed. If more than one operation is specified, the same script should be executed for each of them. If no operation is specified, the script will not be executed (this is meant as poor man's disable feature) </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
tns:ScriptOrderType, simple content |
Defined: |
<xsd:element name="order" type="tns:ScriptOrderType"> <xsd:annotation> <xsd:documentation> Defines the order in which a script is executed. (before or after an operation). </xsd:documentation> </xsd:annotation> </xsd:element> |
This XML schema documentation has been generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.0 template set. DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from
any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually
using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML. DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML,
single-file HTML and RTF output formats. (More formats are planned in the future). A commercial license for "DocFlex/XML XSDDoc" will allow you:
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required! But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only.
And, of course, you could develop any template applications by your own! Please note that by purchasing a license for this software, you not only acquire a useful tool,
you will also make an important investment in its future development, the results of which you could enjoy later by yourself.
Every single your purchase matters and makes a difference for us! To purchase a license, please follow this link: http://www.filigris.com/shop/ |