group "defaultOutboundRouterElements"
Namespace:
http://www.mulesoft.org/schema/mule/core
Content:
2 elements
Defined:
globally in mule.xsd; see XML source
Includes:
definitions of 2 elements
Used:
at 2 locations
Content Model Diagram
Complex Content Model
reply-to?, abstract-transaction?
Content Model Elements (2):
abstract-transaction, reply-to
Known Usage Locations
XML Source (w/o annotations (2); see within schema source)
<xsd:group name="defaultOutboundRouterElements">
<xsd:sequence>
<xsd:element minOccurs="0" name="reply-to" type="endpointRefType"/>
<xsd:element minOccurs="0" ref="abstract-transaction"/>
</xsd:sequence>
</xsd:group>
Content Element Detail (all declarations; defined within this component only; 2/2)
abstract-transaction
Type:
abstractTransactionType, empty content
Abstract:
(may not be used directly in instance XML documents)
Subst.Gr:
may be substituted with 6 elements
Defines an overall transaction that will be used for all endpoints on this router. This is only useful when you want to define an outbound only transaction that will commit all of the transactions defined on the outbound endpoints for this router. Note that you must still define a transaction on each of the endpoints that should take part in the transaction. These transactions should always be configured to JOIN the existing transaction.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" ref="abstract-transaction"/>
reply-to
Type:
endpointRefType, empty content
Defines where the message should be routed after the recipient of the message to which this service dispatches has finished with it.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="reply-to" type="endpointRefType"/>
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.