Schema "mule-bpm.xsd"

Target Namespace:

http://www.mulesoft.org/schema/mule/bpm

Defined Components:

4 global elements, 4 complexTypes

Default Namespace-Qualified Form:

Local Elements: qualified; Local Attributes: unqualified

Schema Location:

http://www.mulesoft.org/schema/mule/bpm/3.3/mule-bpm.xsd; see XML source

Imports Schemas (3):

mule-schemadoc.xsd [src], mule.xsd [src], xml.xsd [src]

Imported by Schema:

_mule-all-included.xsd

Annotation

Support for BPM allows you to send/receive messages to/from a running process. A message from Mule can start or advance a process, the message can be stored as a process variable, and a running process can send messages to any endpoint in your Mule application.

All Element Summary

drools

Type:	droolsType
Content:	complex, 1 attribute, attr. wildcard, 1 element
Subst.Gr:	may substitute for element mule:abstract-extension
Defined:	globally; see XML source
Used:	never

jbpm

Type:	jbpmType
Content:	complex, 3 attributes, attr. wildcard, 1 element
Subst.Gr:	may substitute for element mule:abstract-extension
Defined:	globally; see XML source
Used:	never

process

A process backed by a BPMS such as jBPM.

Type:	processComponentType
Content:	complex, 4 attributes, attr. wildcard, 3 elements
Subst.Gr:	may substitute for elements: mule:abstract-component, mule:abstract-message-processor
Defined:	globally; see XML source
Used:	never

rules

A service backed by a rules engine such as Drools.

Type:	rulesComponentType
Content:	complex, 5 attributes, attr. wildcard, 3 elements
Subst.Gr:	may substitute for elements: mule:abstract-component, mule:abstract-message-processor
Defined:	globally; see XML source
Used:	never

Complex Type Summary

droolsType

Content:	complex, 1 attribute, attr. wildcard, 1 element
Defined:	globally; see XML source
Includes:	definition of 1 attribute
Used:	at 1 location

jbpmType

Content:	complex, 3 attributes, attr. wildcard, 1 element
Defined:	globally; see XML source
Includes:	definitions of 3 attributes
Used:	at 1 location

processComponentType

Content:	complex, 4 attributes, attr. wildcard, 3 elements
Defined:	globally; see XML source
Includes:	definitions of 4 attributes
Used:	at 1 location

rulesComponentType

Content:	complex, 5 attributes, attr. wildcard, 3 elements
Defined:	globally; see XML source
Includes:	definitions of 5 attributes
Used:	at 1 location

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:import namespace="http://www.mulesoft.org/schema/mule/core" schemaLocation="http://www.mulesoft.org/schema/mule/core/3.3/mule.xsd"/>

<xsd:import namespace="http://www.mulesoft.org/schema/mule/schemadoc" schemaLocation="http://www.mulesoft.org/schema/mule/schemadoc/3.3/mule-schemadoc.xsd"/>

<xsd:annotation>

<xsd:documentation>

</xsd:documentation>

<xsd:appinfo>

<schemadoc:short-name>BPM</schemadoc:short-name>

<schemadoc:page-title>BPM Support</schemadoc:page-title>

</xsd:appinfo>

</xsd:annotation>

<xsd:element name="process" substitutionGroup="mule:abstract-component" type="processComponentType">

<xsd:annotation>

<xsd:documentation>

A process backed by a BPMS 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>

An optional reference to the underlying BPMS. This is used to disambiguate in the case where more than one BPMS is available.

</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. The resource type depends on the BPMS being used.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="processIdField" type="xsd:string">

<xsd:annotation>

<xsd:documentation>

This field will be used to correlate Mule messages with processes. If not specified, it will default to MULE_BPM_PROCESS_ID.

</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: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 process in case you have more than one BPMS available.

</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 in this case.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<xsd:element name="rules" substitutionGroup="mule:abstract-component" type="rulesComponentType">

<xsd:annotation>

<xsd:documentation>

A service backed by a rules engine such as Drools.

</xsd:documentation>

</xsd:annotation>

</xsd:element>

<xsd:complexType name="rulesComponentType">

<xsd:complexContent>

<xsd:extension base="mule:abstractComponentType">

<xsd:attribute name="rulesEngine-ref" type="xsd:string">

<xsd:annotation>

<xsd:documentation>

A reference to the underlying Rules Engine.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="rulesDefinition" type="xsd:string" use="required">

<xsd:annotation>

<xsd:documentation>

The resource containing the rules definition. This will be used to deploy the ruleset to the Rules Engine.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="initialFacts-ref" type="xsd:string">

<xsd:annotation>

<xsd:documentation>

A reference to a collection of initial facts to be asserted at startup.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="cepMode" type="xsd:boolean">

<xsd:annotation>

<xsd:documentation>

Are we using the knowledge base for CEP (Complex Event Processing)? (default = false)

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

<xsd:attribute name="entryPoint" type="xsd:string">

<xsd:annotation>

<xsd:documentation>

Entry point for event stream (used by CEP).

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<xsd:element name="drools" substitutionGroup="mule:abstract-extension" type="droolsType"/>

<xsd:complexType name="droolsType">

<xsd:complexContent>

<xsd:extension base="mule:abstractExtensionType">

<xsd:attribute name="name" type="mule:substitutableName">

<xsd:annotation>

<xsd:documentation>

An optional name for this Rules Engine. Refer to this from the "rulesEngine-ref" field of your component in case you have more than one Rules Engine configured.

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

</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.