Schema "mule-jbossts.xsd"
Target Namespace:
http://www.mulesoft.org/schema/mule/jbossts
Defined Components:
global element, 1 complexType
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://www.mulesoft.org/schema/mule/jbossts/3.3/mule-jbossts.xsd; see XML source
Imports Schemas (3):
mule.xsd [src], spring-beans-3.1.xsd [src], xml.xsd [src]
Imported by Schema:
_mule-all-included.xsd
Annotation
This module enables Mule to use the JBoss transaction manager (previously Arjuna) to configure [XA transactions|Transaction Management#XA Transactions]. Developers can configure one Transaction Manger per Mule instance. For more information, see [JBoss Transactions|http://www.jboss.org/jbosstm/].
All Element Summary
transaction-manager To configure an instance of the JBoss transaction manager within Mule, add this element to your Mule XML config file.
Type:
Content:
complex, attr. wildcard, 3 elements
Subst.Gr:
may substitute for element mule:abstract-transaction-manager
Defined:
globally; see XML source
Used:
never
Complex Type Summary
Content:
complex, attr. wildcard, 3 elements
Defined:
globally; see XML source
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/jbossts" xmlns="http://www.mulesoft.org/schema/mule/jbossts" xmlns:mule="http://www.mulesoft.org/schema/mule/core" xmlns:schemadoc="http://www.mulesoft.org/schema/mule/schemadoc" xmlns:spring="http://www.springframework.org/schema/beans" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>
<xsd:annotation>
<xsd:documentation>
This module enables Mule to use the JBoss transaction manager (previously Arjuna) to configure [XA transactions|Transaction Management#XA Transactions]. Developers can configure one Transaction Manger per Mule instance. For more information, see [JBoss Transactions|http://www.jboss.org/jbosstm/].
</xsd:documentation>
<xsd:appinfo>
<schemadoc:short-name>jbossts</schemadoc:short-name>
<schemadoc:page-title>JBoss Transaction Manager</schemadoc:page-title>
</xsd:appinfo>
</xsd:annotation>
<xsd:element name="transaction-manager" substitutionGroup="mule:abstract-transaction-manager" type="transactionManagerType">
<xsd:annotation>
<xsd:documentation>
To configure an instance of the JBoss transaction manager within Mule, add this element to your Mule XML config file. You can configure arbitrary properties on the transaction manager that will be passed on to the underlying transaction manager. For example:
{code:xml}
&lt;jbossts:transaction-manager&gt;
&lt;property key="test" value="TEST"/&gt;
&lt;/jbossts:transaction-manager&gt;
{code}

You can then declare XA transactions on endpoints supporting XA transactions, and all those transactions will be managed by the JBoss transaction manager.

Mule auto-generates the transaction manager XA node ID. To specify the ID yourself, add the following property:

{code:xml}
&lt;jbossts:transaction-manager&gt;
&lt;properties&gt;
&lt;spring:entry key="com.arjuna.ats.arjuna.xa.nodeIdentifier" value="SomeUserNodeId"/&gt;
&lt;/properties&gt;
&lt;/jbossts:transaction-manager&gt;
{code}
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="transactionManagerType">
<xsd:complexContent>
<xsd:sequence>
<xsd:group ref="mule:propertiesGroup"/>
</xsd:sequence>
</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.