xsd.jobXML_1_0.xsd.bak Maven / Gradle / Ivy
Job Specification Language (JSL) specifies a job,
its steps, and directs their execution. JSL also can be referred to
as "Job XML".
This is a helper type. Though it is not otherwise
called out by this name in the specification, it captures the fact
that the xs:string value refers to a batch artifact, across numerous
other JSL type definitions.
The type of a job definition, whether concrete or
abstract. This is the type of the root element of any JSL document.
The job-level properties, which are accessible
via the JobContext.getProperties() API in a batch artifact.
Note that "listeners" sequence order in XML does
not imply order of execution by the batch runtime, per the
specification.
The definition of an job, whether concrete or
abstract. This is the
type of the root element of any JSL document.
This grouping provides allows for the reuse of the
'end', 'fail', 'next', 'stop' element sequences which may appear at
the end of a 'step', 'flow', 'split' or 'decision'. The term
'TransitionElements' does not formally appear in the spec, it is a
schema convenience.
Note that "listeners" sequence order in XML does
not imply order of execution by the batch runtime, per the
specification.
Specifies the checkpoint policy that governs
commit behavior for this chunk. Valid values are: "item" or
"custom". The "item" policy means the chunk is checkpointed after a
specified number of items are processed. The "custom" policy means
the chunk is checkpointed according to a checkpoint algorithm
implementation. Specifying "custom" requires that the
checkpoint-algorithm element is also specified. It is an optional
attribute. The default policy is "item". However, we chose not to
define a schema-specified default for this attribute.
Specifies the number of items to process per
chunk when using the item checkpoint policy. It must be valid XML
integer. It is an optional attribute. The default is 10. The
item-count attribute is ignored for "custom" checkpoint policy.
However, to make it easier for implementations to support JSL
inheritance we abstain from defining a schema-specified default for
this attribute.
Specifies the amount of time in seconds before
taking a checkpoint for the item checkpoint policy. It must be
valid XML integer. It is an optional attribute. The default is 0,
which means no limit. However, to make it easier for
implementations to support JSL inheritance we abstain from defining
a schema-specified default for this attribute.
When a value greater than zero is specified, a checkpoint is taken when
time-limit is reached or item-count items have been processed,
whichever comes first. The time-limit attribute is ignored for
"custom" checkpoint policy.
Specifies the number of exceptions a step will
skip if any configured skippable exceptions are thrown by chunk
processing. It must be a valid XML integer value. It is an optional
attribute. The default is no limit.
Specifies the number of times a step will retry
if any configured retryable exceptions are thrown by chunk
processing. It must be a valid XML integer value. It is an optional
attribute. The default is no limit.
© 2015 - 2024 Weber Informatics LLC | Privacy Policy