element <custom-job-from-message> (global)
Namespace:
http://www.mulesoft.org/schema/mule/quartz
Type:
customFromMessageJobType
Content:
empty, 5 attributes
Subst.Gr:
may substitute for element abstract-job
Defined:
globally in mule-quartz.xsd; see XML source
Used:
never
Content Model Diagram
XML Representation Summary
<custom-job-from-message
   
groupName
 = 
 xsd:string
jobGroupName
 = 
 xsd:string
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" | "process" | "regex" | "string" | "variable" | "xpath" | "xpath2" | "xpath-node" | "custom")
expression
 = 
 xsd:string
custom-evaluator
 = 
 (xsd:string | xsd:NMTOKEN)
/>
May be included in elements by substitutions (3):
endpoint, inbound-endpoint, outbound-endpoint
Annotation
Allows a job to be stored on the current message. This can only be used on outbound endpoints. When the message is received, the job is read and the job is added to the scheduler with the current message. This allows for custom scheduling behavior determined by the message itself. Usually the service or a transformer would create the job on the message based on application-specific logic. Any Mule-supported expressions can be used to read the job from the message. Typically, you add the job as a header, but an attachment could also be used.
XML Source (w/o annotations (1); see within schema source)
<xsd:element name="custom-job-from-message" substitutionGroup="abstract-job" type="customFromMessageJobType"/>
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.