element <transaction-manager>
Namespace:
Type:
Content:
complex, 2 elements
Subst.Gr:
may substitute for element mule:abstract-transaction-manager
Defined:
globally in mule-jbossts.xsd; see XML source
Used:
never
Content Model Diagram
XML Representation Summary
<transaction-manager>
   
Content: 
property*, properties?
</transaction-manager>
Content model elements (2):
May be included in elements by substitutions (1):
Annotation
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} <jbossts:transaction-manager> <property key="test" value="TEST"/> </jbossts:transaction-manager> {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} <jbossts:transaction-manager> <properties> <spring:entry key="com.arjuna.ats.arjuna.xa.nodeIdentifier" value="SomeUserNodeId"/> </properties> </jbossts:transaction-manager> {code}
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="transaction-manager" substitutionGroup="mule:abstract-transaction-manager" type="transactionManagerType"/>

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.