<?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.mulesoft.org/schema/mule/core" schemaLocation="http://www.mulesoft.org/schema/mule/core/3.0/mule.xsd"/> <xsd:import namespace="http://www.mulesoft.org/schema/mule/schemadoc" schemaLocation="http://www.mulesoft.org/schema/mule/schemadoc/3.0/mule-schemadoc.xsd"/> <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:complexContent> <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: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: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: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: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: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: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: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: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: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:complexContent> <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: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:annotation> <xsd:documentation> The configuration file for jBPM, default is "jbpm.cfg.xml" if not specified. </xsd:documentation> </xsd:annotation> </xsd:attribute> <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: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:sequence> <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:annotation> <xsd:documentation> The configuration file for jBPM, default is "jbpm.cfg.xml" if not specified. </xsd:documentation> </xsd:annotation> </xsd:attribute> <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:complexContent mixed="true"> <!-- <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: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: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: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: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> </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: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> </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: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> </xsd:complexContent> </xsd:complexType> <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: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: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. |