XML Schema "mule-bpm.xsd"
Target Namespace:
http://www.mulesoft.org/schema/mule/bpm
Defined Components:
8 global elements, 1 local element, 11 complexTypes, 1 attribute group
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://www.mulesoft.org/schema/mule/bpm/3.0/mule-bpm.xsd; see XML source
Imports Schemas (3):
mule-schemadoc.xsd [src], mule.xsd [src], xml.xsd [src]
Annotation
BPM integration allows process engines to send and receive messages through Mule.
XML Source
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/bpm" xmlns="http://www.mulesoft.org/schema/mule/bpm" xmlns:mule="http://www.mulesoft.org/schema/mule/core" xmlns:schemadoc="http://www.mulesoft.org/schema/mule/schemadoc" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>
<xsd:annotation>
<xsd:documentation>
BPM integration allows process engines to send and receive messages through Mule.
</xsd:documentation>
<xsd:appinfo>
<schemadoc:short-name>BPM</schemadoc:short-name>
<schemadoc:page-title>BPM Integration</schemadoc:page-title>
<schemadoc:transport-features dispatchEvents="true" receiveEvents="true" requestEvents="false" streaming="false" transactions="false">
<schemadoc:MEPs default="one-way" supported="one-way, request-response"/>
</schemadoc:transport-features>
</xsd:appinfo>
</xsd:annotation>
<xsd:element name="process" substitutionGroup="mule:abstract-component" type="processComponentType">
<xsd:annotation>
<xsd:documentation>
A service backed by a process engine such as jBPM.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="processComponentType">
<xsd:complexContent>
<xsd:extension base="mule:abstractComponentType">
<xsd:attribute name="bpms-ref" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A reference to the underlying BPMS, which must implement the {javadoc:mule/transport/bpm|BPMS}org.mule.transport.bpm.BPMS{javadoc} interface to exchange messages through Mule.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="processName" type="xsd:string" use="required">
<xsd:annotation>
<xsd:documentation>
The logical name of the process. This is used to look up the running process instance from the BPMS.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="processDefinition" type="xsd:string" use="required">
<xsd:annotation>
<xsd:documentation>
The resource containing the process definition. This will be used to deploy the process to the BPMS.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="processIdField" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
This field will be used to correlate messages with processes.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="connector" substitutionGroup="mule:abstract-connector" type="bpmConnectorType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="abstractBpmConnectorType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="mule:connectorType">
<xsd:attribute default="false" name="allowGlobalReceiver" type="mule:substitutableBoolean">
<xsd:annotation>
<xsd:documentation>
The global receiver allows an endpoint of type "bpm://*" to receive any incoming message to the BPMS, regardless of the process. If this is false, the process name must be specified for each endpoint. For example, "bpm://MyProcess" will only receive messages for the process "MyProcess".
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="processIdField" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
This field will be used to correlate messages with processes.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="bpmConnectorType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="abstractBpmConnectorType">
<xsd:attribute name="bpms-ref" type="xsd:string" use="required">
<xsd:annotation>
<xsd:documentation>
A reference to the underlying BPMS, which must implement the {javadoc:mule/transport/bpm|BPMS}org.mule.transport.bpm.BPMS{javadoc} interface to exchange messages through Mule using the BPM transport.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="jbpm" substitutionGroup="mule:abstract-extension" type="jbpmType"/>
<xsd:complexType name="jbpmType">
<xsd:complexContent>
<xsd:extension base="mule:abstractExtensionType">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="process-definition" type="processDefinitionType">
<xsd:annotation>
<xsd:documentation>
A process definition to be loaded into jBPM at startup.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="name" type="mule:substitutableName">
<xsd:annotation>
<xsd:documentation>
An optional name for this BPMS. Refer to this from the "bpms-ref" field of your component in case you have more than one BPMS configured.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="configurationResource" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The configuration file for jBPM, default is "jbpm.cfg.xml" if not specified.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="processEngine-ref" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A reference to the already-initialized jBPM ProcessEngine. This is useful if you use Spring to configure your jBPM instance. Note that the "configurationResource" attribute will be ignored.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="jbpm-connector" substitutionGroup="mule:abstract-connector" type="jBpmConnectorType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="jBpmConnectorType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="abstractBpmConnectorType">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" name="process-definition" type="processDefinitionType">
<xsd:annotation>
<xsd:documentation>
A process definition to be loaded into jBPM when the connector is initialized.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="configurationResource" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The configuration file for jBPM, default is "jbpm.cfg.xml" if not specified.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="processEngine-ref" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A reference to the already-initialized jBPM ProcessEngine. This is useful if you use Spring to configure your jBPM instance. Note that the "configurationResource" attribute will be ignored.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="processDefinitionType">
<xsd:complexContent mixed="true">
<xsd:extension base="mule:abstractExtensionType">
<!--
<xsd:sequence>
<xsd:element name="text" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Used for embedding the process definition inside the XML. This is useful for simple processes where you are just mocking up a quick application.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
-->
<xsd:attribute name="name" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The process definition file. The file can be on the classpath or local file system.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="resource" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The process definition file. The file can be on the classpath or local file system.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="customElement">
<xsd:choice>
<xsd:any maxOccurs="unbounded" minOccurs="0" namespace="##any" processContents="lax"/>
</xsd:choice>
<xsd:anyAttribute namespace="##any" processContents="lax"/>
</xsd:complexType>
<xsd:element name="inbound-endpoint" substitutionGroup="mule:abstract-inbound-endpoint" type="inboundEndpointType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="inboundEndpointType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="mule:inboundEndpointType">
<xsd:attributeGroup ref="addressAttributes"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="outbound-endpoint" substitutionGroup="mule:abstract-outbound-endpoint" type="outboundEndpointType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="outboundEndpointType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="mule:outboundEndpointType">
<xsd:attributeGroup ref="addressAttributes"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="endpoint" substitutionGroup="mule:abstract-global-endpoint" type="globalEndpointType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="globalEndpointType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="mule:globalEndpointType">
<xsd:attributeGroup ref="addressAttributes"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:attributeGroup name="addressAttributes">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="process" type="xsd:string"/>
</xsd:attributeGroup>
<!--
This is merely a shortcut for:
<endpoint-selector-router selectorExpression="header:MULE_BPM_ENDPOINT">
-->
<xsd:element name="outbound-router" substitutionGroup="mule:abstract-outbound-router" type="bpmOutboundRouterType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="bpmOutboundRouterType">
<xsd:annotation>
<xsd:documentation>
Deprecated: It is recommended to configure BPM as a component rather than a transport for 3.x
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>

XML schema documentation generated with DocFlex/XML SDK 1.8.1b6 using DocFlex/XML XSDDoc 2.2.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.