complexType "abstractExceptionStrategyType"
Namespace:
Content:
complex, 1 attribute, 2 elements
Defined:
globally in mule.xsd; see XML source
Includes:
definitions of 1 attribute, 2 elements
Used:
Content Model Diagram
XML Representation Summary
<...
    enableNotifications
 = 
xsd:boolean
    >
   
Content: 
commit-transaction?, rollback-transaction?
</...>
Content Model Elements (2):
Known Direct Subtypes (2):
Known Indirect Subtypes (1):
All Direct / Indirect Based Elements (4):
Known Usage Locations
XML Source (w/o annotations (3); see within schema source)
<xsd:complexType name="abstractExceptionStrategyType">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="commit-transaction" type="exceptionPatternType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="rollback-transaction" type="exceptionPatternType"/>
</xsd:sequence>
<xsd:attribute name="enableNotifications" type="xsd:boolean"/>
</xsd:complexType>
Attribute Detail (all declarations; defined in this component only; 1/1)
enableNotifications
Type:
xsd:boolean, predefined
Use:
optional
Determines whether ExceptionNotifications will be fired from this strategy when an exception occurs. Default is true.
XML Source (w/o annotations (1); see within schema source)
<xsd:attribute name="enableNotifications" type="xsd:boolean"/>
Content Element Detail (all declarations; defined in this component only; 2/2)
commit-transaction
Type:
exceptionPatternType, empty content
Defines when a current transaction gets committed based on the name of the exception caught. You can set a comma-separated list of wildcard patterns that will be matched against the fully qualified classname of the current exception. Patterns defined for this element will leave the current transaction (if any) untouched and allow it to be committed.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="commit-transaction" type="exceptionPatternType"/>

rollback-transaction
Type:
exceptionPatternType, empty content
Defines when a current transaction gets rolled back based on the name of the exception caught. You can set a comma-separated list of wildcard patterns that will be matched against the fully qualified classname of the current exception. Patterns defined for this element will roll back the current transaction (if any).
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="rollback-transaction" type="exceptionPatternType"/>

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.