XML Schema "lumis-component-script.xsd"
Target Namespace:
http://www.lumis.com.br/lumisportal/xsd/component-install-script
Components:
7 local elements, 5 complexTypes, 1 element group
Schema Location:
/data/jenkins-slave/home1/data/workspace/lpjava-10.2.x-dist/repo/Lumis_PortalJava/distribution/tmp/deployment/lumis-component-script.xsd, see XML source
Included in Schema:
lumis-component-install-script.xsd [src]
All Element Summary
class (type xsd:string) The class that will be executed in this step.
Type:
xsd:string
Content:
simple
Defined:
locally at 1 location
environment (within environments) Define an environment that this step will run into.
Type:
embedded complexType
Content:
empty, 2 attributes
Defined:
locally at 1 location
Includes:
definitions of 2 attributes
environments (within execute-database-file) Defines which environments should run this step.
Type:
embedded complexType
Content:
complex, 2 attributes, 1 element
Defined:
locally at 1 location
Includes:
definition of 1 element
message (type xsd:string) The message that will be displayed when this step is displayed.
Type:
xsd:string
Content:
simple
Defined:
locally at 2 locations
parameter (within parameters) A parameter that will be passed to the executable.
Type:
embedded (extension of xsd:string)
Content:
simple, 1 attribute
Defined:
locally at 1 location
Includes:
definition of 1 attribute
parameters (within run-class) Defines the parameters that will be passed to the executable.
Type:
embedded complexType
Content:
complex, 1 attribute, 1 element
Defined:
locally at 1 location
Includes:
definition of 1 element
sql (within run-sql) Provides an SQL command to be ran.
Type:
embedded (extension of xsd:string)
Content:
simple, 1 attribute
Defined:
locally at 1 location
Includes:
definition of 1 attribute
Complex Type Summary
lum_displayMessage
Content:
complex, 1 element
Includes:
definition of 1 element
Used:
at 1 location
lum_removeGlobalNonReferencedEntries
Content:
empty
Used:
at 1 location
lum_runJavaClass
Content:
complex, 1 attribute, 2 elements
Includes:
definitions of 2 elements
Used:
at 1 location
lum_runSqlStep
Content:
complex, 1 attribute, 1 element
Includes:
definition of 1 element
Used:
at 1 location
lum_scriptStep
Content:
empty
Used:
at 1 location
Element Group Summary
genericStep
Content:
2 elements
Includes:
definitions of 2 elements
Used:
at 1 location
XML Source
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Revision: 16974 $ $Date: 2015-02-20 13:16:28 +0000 (Fri, 20 Feb 2015) $ -->
<xsd:complexType name="lum_scriptStep">
</xsd:complexType>
<xsd:complexType name="lum_runSqlStep">
<xsd:complexContent>
<xsd:extension base="lum_scriptStep">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="sql">
<xsd:annotation>
<xsd:documentation>
Provides an SQL command to be ran. Although more than one "sql" element can be added, only one will be ran. The possibility of adding more than one "sql" element is to make it possible to have different versions of the same SQL to be executed in different database engines.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="database-type">
<xsd:annotation>
<xsd:documentation>
<![CDATA[
Restricts this SQL execution to the given database.<br />
<ul>
<li>oracle: for Oracle database.</li>
<li>sqlserver: for Microsoft SQL Server database.</li>
<li>mysql: for MySQL database.</li>
</ul>
]]>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="oracle"/>
<xsd:enumeration value="sqlserver"/>
<xsd:enumeration value="mysql"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
<xsd:group ref="genericStep"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_runJavaClass">
<xsd:complexContent>
<xsd:extension base="lum_scriptStep">
<xsd:sequence>
<xsd:element name="class" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
<![CDATA[
The class that will be executed in this step. The given class <em>must</em> implement lumis.portal.deployment.script.IStepExecutable.
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="parameters">
<xsd:annotation>
<xsd:documentation>
Defines the parameters that will be passed to the executable. These parameters will be condensed into a map (java.util.Map). For that reason, two parameters with the very same name are not expected to coexist.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence maxOccurs="unbounded">
<xsd:element name="parameter">
<xsd:annotation>
<xsd:documentation>
A parameter that will be passed to the executable. This node content will be the value of the parameter. The parameter name is defined through the attribute "name".
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attribute name="name" use="required">
<xsd:annotation>
<xsd:documentation>
The parameter name.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:group ref="genericStep"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_displayMessage">
<xsd:complexContent>
<xsd:extension base="lum_scriptStep">
<xsd:sequence>
<xsd:element name="message" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The message that will be displayed when this step is displayed.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="genericStep"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="lum_removeGlobalNonReferencedEntries">
<xsd:complexContent>
<xsd:extension base="lum_scriptStep">
<xsd:group ref="genericStep"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:group name="genericStep">
<xsd:sequence>
<xsd:element minOccurs="0" name="environments">
<xsd:annotation>
<xsd:documentation>
Defines which environments should run this step. If at least one of the defined environments match the current environment then this step will be executed. Otherwise it will be automatically ignored.
If this node is suppressed, then this step will be run in all environments.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="environment">
<xsd:annotation>
<xsd:documentation>
Define an environment that this step will run into. At least one of "tag" or "type" parameters are required. It will match the current environment if the provided tag (if any) is present in the current environment and if the given environment type (if any) is equal to the current environment's one.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute name="tag" use="optional">
<xsd:annotation>
<xsd:documentation>
The required environment tag.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="1"/>
<xsd:maxLength value="255"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="type" use="optional">
<xsd:annotation>
<xsd:documentation>
The required environment type.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="development"/>
<xsd:enumeration value="structure building"/>
<xsd:enumeration value="user acceptance"/>
<xsd:enumeration value="production"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="message" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The message that will be displayed when this step is displayed.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
</xsd:schema>
XML Schema documentation generated with DocFlex/XML (Kit) v1.6.2
DocFlex/XML is a powerful template-driven documentation and report generator from any data stored in XML files. Based on an innovative technology developed by FILIGRIS WORKS, this new tool offers virtuoso data querying and formatting capabilities not found in anything else!
Need to convert your XML data into a clear nice-looking documentation or reports? Web-ready hypertext HTML or printable MS Word / OpenOffice.org friendly RTF? DocFlex/XML may be a cheap, quick and effective solution exactly for this task!
Have questions? Not sure how to use it? Just send us e-mail to contact@filigris.com and we are always happy to help you! See also our services at www.filigris.com

Lumisportal  10.2.0.170730 - Copyright © 2006–2017 Lumis EIP Tecnologia da Informação LTDA. All Rights Reserved.