element <async-reply> (local)
Namespace:
Type:
Content:
complex, 2 attributes, 5 elements
Defined:
locally witnin baseServiceType complexType in mule.xsd; see XML source
Content Model Diagram
XML Representation Summary
<async-reply
   
 = 
(xsd:string | xsd:int)
 = 
(xsd:string | xsd:boolean)
    >
   
Content: 
abstract-inbound-endpoint+, (abstract-async-reply-router | abstract-inbound-router | processor | custom-processor)*
</async-reply>
Content model elements (5):
abstract-async-reply-router, abstract-inbound-endpoint, abstract-inbound-router, custom-processor, processor
Included in content model of elements (2):
custom-service, service
May contain elements by substitutions (43):
collection-aggregator-router, collection-async-reply-router, correlation-resequencer-router, custom-async-reply-router, custom-correlation-aggregator-router, custom-inbound-router, forwarding-router, idempotent-receiver-router, idempotent-secure-hash-receiver-router, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, inbound-endpoint, message-chunking-aggregator-router, selective-consumer-router, servlet-inbound-endpoint, single-async-reply-router, wire-tap-router
Annotation
The elements within 'async-reply' describe how asynchronous replies are handled.
XML Source (w/o annotations (1); see within schema source)
<xsd:element minOccurs="0" name="async-reply" type="asyncReplyCollectionType"/>

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.