complexType "whenMessageProcessorFilterPairType"
Namespace:
Content:
complex, 3 attributes, 3 elements
Defined:
globally in mule.xsd; see XML source
Includes:
definitions of 3 attributes, 1 element
Used:
Content Model Diagram
XML Representation Summary
<...
    evaluator
 = 
("attachment" | "attachments" | "attachments-list" | "bean" | "endpoint" | "exception-type" | "function" | "groovy" | "header" | "headers" | "headers-list" | "json" | "json-node" | "jxpath" | "map-payload" | "message" | "mule" | "ognl" | "payload" | "payload-type" | "processor" | "regex" | "string" | "wildcard" | "xpath" | "xpath-node" | "custom")
    expression
 = 
xsd:string
    custom-evaluator
 = 
(xsd:string | xsd:NMTOKEN)
    >
   
Content: 
abstract-filter?, (abstract-message-processor | abstract-outbound-endpoint)
</...>
Content Model Elements (3):
All Direct / Indirect Based Elements (1):
Known Usage Locations
Type Definition Detail
Type Derivation Tree
  whenMessageProcessorFilterPairType
XML Source (w/o annotations (4); see within schema source)
<xsd:complexType name="whenMessageProcessorFilterPairType">
<xsd:complexContent>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="abstract-filter"/>
<xsd:group maxOccurs="1" minOccurs="1" ref="messageProcessorOrOutboundEndpoint"/>
</xsd:sequence>
<xsd:attribute name="evaluator" type="standardExpressionEvaluators" use="optional"/>
<xsd:attribute name="expression" type="xsd:string" use="optional"/>
<xsd:attribute name="custom-evaluator" type="substitutableName" use="optional"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Attribute Detail (all declarations; defined in this component only; 3/3)
custom-evaluator
Type:
Use:
optional
The name of the custom evaluator to use. This attribute is only used when the 'evaluator' attribute is set to "custom". You can plug in your own expression evaluators by registering them with the ExpressionEvaluatorManager.
Attribute Value
xsd:string | xsd:NMTOKEN
XML Source (w/o annotations (1); see within schema source)
<xsd:attribute name="custom-evaluator" type="substitutableName" use="optional"/>

evaluator
Type:
Use:
optional
The expression evaluator to use. Expression evaluators must be registered with the ExpressionEvaluatorManager before they can be used. Using the custom evaluator allows you to define your own evaluator with the 'custom-evaluator' attribute. Note that some evaluators such as xpath, groovy, and bean are loaded from other Mule modules (XML and Scripting, respectively). These modules must be on your classpath before the evaluator can be used.
Attribute Value
enumeration of (xsd:string | xsd:NMTOKEN)
Enumeration:
"attachment", "attachments", "attachments-list", "bean", "endpoint", "exception-type", "function", "groovy", "header", "headers", "headers-list", "json", "json-node", "jxpath", "map-payload", "message", "mule", "ognl", "payload", "payload-type", "processor", "regex", "string", "wildcard", "xpath", "xpath-node", "custom"
XML Source (w/o annotations (1); see within schema source)
<xsd:attribute name="evaluator" type="standardExpressionEvaluators" use="optional"/>

expression
Type:
xsd:string, predefined
Use:
optional
The expression to evaluate. The syntax of this attribute changes depending on the evaluator being used.
XML Source (w/o annotations (1); see within schema source)
<xsd:attribute name="expression" type="xsd:string" use="optional"/>
Content Element Detail (all declarations; defined in this component only; 1/3)
abstract-filter
Type:
abstractFilterType, empty content
Abstract:
(may not be used directly in instance XML documents)
Subst.Gr:
affiliated to substitution group abstract-message-processor; may be substituted with 28 elements
The condition to use to decide if the message processor can be used. Can't be used if an expression attribute has been defined on the when element.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" ref="abstract-filter"/>

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.