element <expression-recipient-list-router>
Namespace:
Type:
Content:
complex, 7 attributes, 5 elements
Subst.Gr:
may substitute for element abstract-outbound-router
Defined:
globally in mule.xsd; see XML source
Used:
never
Content Model Diagram
XML Representation Summary
<expression-recipient-list-router
    enableCorrelation
 = 
("ALWAYS" | "NEVER" | "IF_NOT_SET") : "IF_NOT_SET"
    transformer-refs
 = 
xsd:NMTOKENS
    useTemplates
 = 
(xsd:string | xsd:boolean) : "true"
    evaluator
 = 
("attachment" | "attachments" | "attachments-list" | "bean" | "endpoint" | "exception-type" | "function" | "groovy" | "header" | "headers" | "headers-list" | "jxpath" | "map-payload" | "message" | "mule" | "ognl" | "payload" | "payload-type" | "regex" | "string" | "wildcard" | "xpath" | "xpath-node" | "custom")
    expression
 = 
xsd:string
    custom-evaluator
 = 
(xsd:string | xsd:NMTOKEN)
    synchronous
 = 
xsd:boolean
    >
   
Content: 
reply-to?, abstract-transaction?, abstract-filter?, abstract-transformer*, recipients?
</expression-recipient-list-router>
Content model elements (5):
May contain elements by substitutions (93):
and-filter, append-string-transformer, auto-transformer, base64-decoder-transformer, base64-encoder-transformer, bean-builder-transformer, bean-to-map-transformer, body-to-parameter-map-transformer, byte-array-to-hex-string-transformer, byte-array-to-object-transformer, byte-array-to-serializable-transformer, byte-array-to-string-transformer, bytes-to-mime-transformer, client-ack-transaction, custom-filter, custom-transaction, custom-transformer, decrypt-transformer, dom-to-output-handler-transformer, dom-to-xml-transformer, email-to-string-transformer, encrypt-transformer, entry-builder-transformer, exception-type-filter, expression-filter, expression-transformer, file-to-byte-array-transformer, file-to-string-transformer, filename-regex-filter, filename-wildcard-filter, filter, filter, filter, gzip-compress-transformer, gzip-uncompress-transformer, hex-string-to-byte-array-transformer, http-request-to-byte-array, http-request-to-input-stream, http-request-to-parameter-map, http-response-to-object-transformer, http-response-to-string-transformer, http-to-soap-request-transformer, is-json-filter, is-xml-filter, jaxb-object-to-xml-transformer, jaxb-xml-to-object-transformer, jaxen-filter, jmsmessage-to-object-transformer, json-to-object-transformer, jxpath-extractor-transformer, jxpath-filter, map-to-bean-transformer, message-properties-transformer, message-property-filter, message-to-http-response-transformer, mime-to-bytes-transformer, not-filter, object-to-byte-array-transformer, object-to-http-request-transformer, object-to-jmsmessage-transformer, object-to-json-transformer, object-to-mime-transformer, object-to-string-transformer, object-to-xml-transformer, object-to-xmpp-transformer, or-filter, payload-type-filter, property-filter, regex-filter, request-wildcard-filter, route-filter, schema-validation-filter, schema-validation-transformer, serializable-to-byte-array-transformer, string-to-byte-array-transformer, string-to-email-transformer, transaction, transaction, transaction, transformer, transformer, wildcard-filter, xa-transaction, xml-entity-decoder-transformer, xml-entity-encoder-transformer, xml-prettyprinter-transformer, xml-to-dom-transformer, xml-to-object-transformer, xmpp-to-object-transformer, xpath-extractor-transformer, xpath-filter, xquery-transformer, xslt-transformer
May be included in elements by substitutions (2):
Annotation
Sends the same message to multiple endpoints over the same endpoint, or implements routing-slip behavior where the next destination for the message is determined from message properties or the payload. The recipients can be extracted from the message using an expression, or you can specify a static list of recipient endpoints. (As of version 2.1)
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="expression-recipient-list-router" substitutionGroup="abstract-outbound-router" type="expressionOrStaticRecipientListRouterType"/>

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.