You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+43-5Lines changed: 43 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -24,14 +24,52 @@ The workflow scheduler analyzes dependencies and executes participating flows in
24
24
25
25
In order for a Spring-Batch flow to participate in a workflow, it must adhere to the following requirements:
26
26
27
-
* must accept its input only via a`input` job parameter. This parameter must be encoded as a semicolon-separated list of absolute file paths.
27
+
* must accept its input only via an`input` or `input.<key>` job parameter. This parameter must be encoded as a semicolon-separated list of absolute file paths.
28
28
* must publish an `outputDir` entry to its execution context. This entry must contain the absolute path of the job-wide output directory, and this will be used to resolve all outputs expected by this job node.
29
29
30
-
## Describe a workflow
31
-
32
-
__Todo__
30
+
## Build a workflow
31
+
32
+
A workflow is built on top of Spring Batch flows. An example taken from project's tests:
A workflow is executed (started or restarted) by a workflow scheduler (interface `eu.slipo.workflows.service.WorkflowScheduler`). Currently, the only implementation is the
0 commit comments