The task to be executed is defined by the nested jobs which may use the properties. which will be defined when executing the tasks.
This implementation only supports the single execution of a task at one time. If the task is running additional requests to execute the task will be ignored.
Future version will support multiple parallel executions of tasks.
| arooaSession | |
| job | The job to pass resets on to. |
| name | A name, can be any text. |
| parameterInfo | |
| properties | |
| requests | |
| reset | |
| response |
| Example 1 | A Task Service that greets people by name. |
| Configured By | ELEMENT |
| Access | WRITE_ONLY |
| Configured By | ELEMENT |
| Access | WRITE_ONLY |
| Required | Yes. |
The job to pass resets on to.
| Configured By | ATTRIBUTE |
| Access | READ_WRITE |
| Required | No. |
A name, can be any text.
| Access | READ_ONLY |
| Access | READ_ONLY |
| Configured By | ELEMENT |
| Access | READ_WRITE |
| Configured By | ATTRIBUTE |
| Access | READ_WRITE |
| Configured By | ATTRIBUTE |
| Access | READ_WRITE |
A Task Service that greets people by name. Three task-requests call the service with different names.
<oddjob>
<job>
<sequential>
<jobs>
<task-service id="hello-service">
<requests>
<input-text prompt="Name" property="some.name"/>
</requests>
<job>
<echo>Hello ${some.name}.</echo>
</job>
</task-service>
<task-request taskExecutor="${hello-service}">
<properties>
<properties>
<values>
<value key="some.name" value="Rod"/>
</values>
</properties>
</properties>
</task-request>
<task-request taskExecutor="${hello-service}">
<properties>
<properties>
<values>
<value key="some.name" value="Jane"/>
</values>
</properties>
</properties>
</task-request>
<task-request taskExecutor="${hello-service}">
<properties>
<properties>
<values>
<value key="some.name" value="Freddy"/>
</values>
</properties>
</properties>
</task-request>
</jobs>
</sequential>
</job>
</oddjob>