represents the job submission. As the job repo is heterogeneous, it could match anything really that's asking for work
Adds some key/value data to the submission details
Adds some key/value data to the submission details
the key/value pair
an updated SubmitJob with the given key/value
represents the job submission.
represents the job submission. As the job repo is heterogeneous, it could match anything really that's asking for work
the jobId from the submission details, if given
the work subscription
the logic which will compare the job w/ the subscription
true if this job can match the given subscription
the new submission matcher
a new SubmitJob using the given details matcher
Specifies a fallback work subscription to use if the original one doesn't match
Specifies a fallback work subscription to use if the original one doesn't match
the json matching criteria
an updated SubmitJob with the given 'orElse' criteria specified
a submit job with the 'orElse' criteria for the submission details, if specified
whether or not this submission should block (wait for a work match) in the exchange (when true) or follow fire-and-forget semantics (when false)
a copy of the submitjob with the 'awaitMatch' flag set
Append the data as a json block to the submission details
Append the data as a json block to the submission details
the type of the data to append
the data to append
the json name of the element. If left unspecified, the simple classname of the data type is used.
the new submit job with the given data appended under the name, if specified
a copy of the submitjob with the given submission details
Means to append a jobId to the SubmitJob
Means to append a jobId to the SubmitJob
the current weather in Tokyo
a new SubmitJob with a jobId specified in the submission details
the new SelectionMode
an updated job which uses the given selection mode
(Since version ) see corresponding Javadoc for more information.
Represents anything which can be run as a job, together with some submissionDetails which are used to instruct the Exchange.
Where a basic REST endpoint would typically be POSTed some json data, a 'SubmitJob' acts as an envelope for that 'job', pairing it with some additional SubmissionDetails.
The Exchange can then use both the job and submission details to match work with pulling work subscriptions based on the criteria/selection mode/etc specified by the submission details and work subscription.
represents the job submission. As the job repo is heterogeneous, it could match anything really that's asking for work