Schema "mule-test.xsd"
Target Namespace:
http://www.mulesoft.org/schema/mule/test
Defined Components:
global elements, 2 local elements, 1 complexType
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://www.mulesoft.org/schema/mule/test/3.3/mule-test.xsd; see XML source
Imports Schemas (2):
mule.xsd [src], xml.xsd [src]
Imported by Schema:
_mule-all-included.xsd
All Element Summary
assert A transformer that has no effect.
Type:
anonymous complexType (extension of mule:abstractMessageProcessorType)
Content:
complex, 3 attributes, attr. wildcard, 1 element
Subst.Gr:
may substitute for element mule:abstract-message-processor
Defined:
globally; see XML source
Includes:
definitions of 3 attributes
Used:
never
callback A user-defined callback that is invoked when the test component is invoked.
Type:
anonymous complexType
Content:
empty, 1 attribute
Defined:
locally witnin testComponentType complexType; see XML source
Includes:
definition of 1 attribute
component A component that can be used for testing message flows.
Type:
Content:
complex, 10 attributes, attr. wildcard, 5 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
never
connector
Type:
Content:
complex, 4 attributes, attr. wildcard, 6 elements
Subst.Gr:
may substitute for element mule:abstract-connector
Defined:
globally; see XML source
Used:
never
no-action-transformer A transformer that has no effect.
Type:
Content:
complex, 5 attributes, attr. wildcard, 1 element
Subst.Gr:
Defined:
globally; see XML source
Used:
never
return-data Defines the data to return from the service once it has been invoked.
Type:
anonymous complexType
Content:
mixed (allows character data), 1 attribute
Defined:
locally witnin testComponentType complexType; see XML source
Includes:
definition of 1 attribute
web-service-component A component that can be used for testing web services.
Type:
Content:
complex, 10 attributes, attr. wildcard, 5 elements
Subst.Gr:
Defined:
globally; see XML source
Used:
never
Complex Type Summary
Content:
complex, 10 attributes, attr. wildcard, 5 elements
Defined:
globally; see XML source
Includes:
definitions of 10 attributes, 2 elements
Used:
XML Source
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/test" xmlns="http://www.mulesoft.org/schema/mule/test" xmlns:mule="http://www.mulesoft.org/schema/mule/core" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>
<xsd:element name="connector" substitutionGroup="mule:abstract-connector" type="mule:connectorType"/>
<xsd:element name="component" substitutionGroup="mule:abstract-component" type="testComponentType">
<xsd:annotation>
<xsd:documentation>
A component that can be used for testing message flows. It is a configurable component. The return data for the component can be set so that users can simulate a call to a real service. This component can also track invocation history and fire notifications when messages are received.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="web-service-component" substitutionGroup="mule:abstract-component" type="testComponentType">
<xsd:annotation>
<xsd:documentation>
A component that can be used for testing web services. This component has the same properties as {{component}} element, but in addition to implementing {{org.mule.api.lifecycle.Callable}}, it also implements {{org.mule.api.component.simple.EchoService}}, {{org.mule.tck.testmodels.services.DateService}}, and {{org.mule.tck.testmodels.services.PeopleService}}. When using this with WS endpoints such as CXF, be sure to set the {{serviceClass}} property of the endpoint to the type of service you are using.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="testComponentType">
<xsd:complexContent>
<xsd:extension base="mule:abstractComponentType">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="return-data">
<xsd:annotation>
<xsd:documentation>
Defines the data to return from the service once it has been invoked. The return data can be located in a file, which you specify using the {{file}} attribute (specify a resource on the classpath or on disk), or the return data can be embeddded directly in the XML.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType mixed="true">
<xsd:attribute name="file" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The location of a file to load. The file can point to a resource on the classpath or on disk.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="callback">
<xsd:annotation>
<xsd:documentation>
A user-defined callback that is invoked when the test component is invoked. This can be useful for capturing information such as message counts. Use the {{class}} attribute to specify the callback class name, which must be an object that implements {{org.mule.tck.functional.EventCallback}}.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute name="class" type="xsd:string" use="required">
<xsd:annotation>
<xsd:documentation>
A class name of an object that implements {{org.mule.tck.functional.EventCallback}}.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="throwException" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the component should throw an exception before any processing takes place.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="logMessageDetails" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether to output all message details to the log. This includes all headers and the full payload. The information will be loogged at INFO level.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="doInboundTransform" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether the message will be transformed using the transformer(s) set on the inbound endpoint before it gets processed. The default is true.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="exceptionToThrow" type="mule:substitutableName">
<xsd:annotation>
<xsd:documentation>
A fully qualified classname of the exception object to throw. Used in conjunction with {{throwException}}. If this is not specified, a {{FunctionalTestException}} will be thrown by default.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="exceptionText" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The text of the exception that is thrown. Used in conjunction with {{throwException}}. If this is not specified, an empty message will be used.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="enableMessageHistory" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Every message that is received by the test component is stored and can be retrieved. If you do not want this information stored, such as if you are running millions of messages through the component, you can disable this feature to avoid a potential out of memory error.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="enableNotifications" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether to fire a {{FunctionalTestNotification}} when a message is received by the component. Test cases can register to receive these notifications and make assertions on the current message.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="appendString" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A string value that will be appeneded to every message payload that passes through the component. Note that by setting this property you implicitly select that the message payload will be converted to a string and that a string payload will be returned. The inbound transformer (if any) will get applied first, but if that does not return a string, {{MuleEventContext.getMessageAsString()}} will be called directly after.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="waitTime" type="mule:substitutableLong">
<xsd:annotation>
<xsd:documentation>
The time in milliseconds to wait before returning a result. All processing happens in the component before the wait begins.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="id" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The name of this component
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="no-action-transformer" substitutionGroup="mule:abstract-transformer" type="mule:abstractTransformerType">
<xsd:annotation>
<xsd:documentation>
A transformer that has no effect.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="assert" substitutionGroup="mule:abstract-message-processor">
<xsd:annotation>
<xsd:documentation>
A transformer that has no effect.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="mule:abstractMessageProcessorType">
<xsd:attribute name="expression" use="required"/>
<xsd:attribute name="message"/>
<xsd:attribute name="count" type="xsd:string"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</xsd:schema>

XML schema documentation generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.0 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.