skip to main content
Corticon Server: Integration & Deployment Guide : Service contract examples : Examples of XSD and WSDLS available in the Deployment Console : 1 Vocabulary-level XML schema, FLAT XML messaging style : 1.4 MessagesType
 

Try Corticon Now
1.4 MessagesType
<xsd:complexType name=MessagesType>
If you plan to use a software tool to read and use a Corticon-generated service contract, be sure it supports this <xsd:sequence> tag (see important note below)…
<xsd:sequence>
A Messages element includes zero or more Message elements.
<xsd:element name=Message type=tns:MessageType minOccurs=0
maxOccurs=unbounded />
  </xsd:sequence>
This version number corresponds to the responding Decision Service's version number, which is set in Corticon Studio.
<xsd:attribute name=version type=xsd:string />
</xsd:complexType>
A Message element consists of several items – see the Rule Language Guide for more information on the post operator, which generates the components of a Messages element.
<xsd:complexType name=MessageType>
  <xsd:sequence>
These severity levels correspond to those of the posted Rule Statements…
<xsd:element name=severity>
      <xsd:simpleType>
         <xsd:restriction base=xsd:string>
            <xsd:enumeration value=Info />
            <xsd:enumeration value=Warning />
            <xsd:enumeration value=Violation />
         </xsd:restriction>
      </xsd:simpleType>
</xsd:element>
The text element corresponds to the text of the posted Rule Statements…
<xsd:element name=text type=xsd:string />
<xsd:element name=entityReference>
      <xsd:complexType>
The href association corresponds to the entity references of the posted Rule Statements…
<xsd:attribute name=href type=xsd:anyURI />
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
The XML tag <xsd:sequence> is used to define the attributes of a given element. In an XML Schema, <sequence> requires the elements that follow to appear in exactly the order defined by the schema within the corresponding XML document.
If CcServer.properties com.corticon.ccserver.ensureComplianceWithServiceContract is:
*true, the Server will return the elements in the same order as specified by the service contract, even for elements created during rule execution and not present in the incoming message.
*false, the Server may return elements in any order. Consuming applications should be designed accordingly. This setting results in slightly better Server performance.