element <tns:script> (local)
Namespace:
Type:
Content:
complex, 6 elements
Defined:
locally witnin tns:ScriptsType complexType in common-1.xsd; see XML source
XML Representation Summary
<tns:script>
   
Content: 
tns:operation*, tns:order, tns:host?, tns:language, tns:argument*, tns:code
</tns:script>
Content model elements (6):
tns:argument (in tns:script), tns:code (in tns:script), tns:host (in tns:script), tns:language (type xsd:anyURI), tns:operation (in tns:script), tns:order (in tns:script)
Included in content model of elements (1):
tns:scripts
Annotation
Specific script definition. Note: More than one script definition may apply to a specific operation.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="script" type="tns:ScriptType">
<xsd:annotation>
<xsd:documentation>
Specific script definition.
Note: More than one
script definition may apply to a
specific
operation.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
Content Element Detail (all declarations; 6/6)
tns:argument
Type:
tns:ScriptArgumentType, complex content
Defined:
locally within tns:ScriptType complexType
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.
XML Source (see within schema source)
<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>

tns:code
Type:
xsd:string, simple content
Defined:
locally within tns:ScriptType complexType
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).
XML Source (see within schema source)
<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>

tns:host
Type:
tns:ScriptHostType, simple content
Default:
"resource"
Defined:
locally within tns:ScriptType complexType
Defines where the script should be executed (connector or resource). If no type is specified, it defaults to resource.
XML Source (see within schema source)
<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>

tns:language
Type:
xsd:anyURI, simple content
Defined:
locally within tns:ScriptType complexType
Specifies the language of the script.
XML Source (see within schema source)
<xsd:element name="language" type="xsd:anyURI">
<xsd:annotation>
<xsd:documentation>
Specifies the language of the script.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

tns:operation
Type:
tns:OperationTypeType, simple content
Defined:
locally within tns:ScriptType complexType
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)
XML Source (see within schema source)
<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>

tns:order
Type:
tns:ScriptOrderType, simple content
Defined:
locally within tns:ScriptType complexType
Defines the order in which a script is executed. (before or after an operation).
XML Source (see within schema source)
<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:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
  • To include only XML schema components specified by name.
  • To document local element components both globally and locally (similar to attributes).
  • To allow/suppress unification of local elements by type.
  • To enable/disable reproducing of namespace prefixes.
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To remove this very advertisement text!
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/