Abstract base class for Job Commands Implementations
@author Sergio Montoro Ten @version 5.0User: Zhang Kaitao
Date: 13-2-4 上午9:38
Version: 1.0
{ "command" : [ "server", "serverconfig.yaml" ], "env" : { "JVM_ARGS" : "-Ddw.feature.randomFeatureFlagEnabled=true" }, "expires" : null, "id" : "myservice:0.5:3539b7bc2235d53f79e6e8511942bbeaa8816265", "image" : "myregistry:80/janedoe/myservice:0.5-98c6ff4", "ports" : { "http" : { "externalPort" : 8060, "internalPort" : 8080, "protocol" : "tcp" }, "http-admin" : { "externalPort" : 8061, "internalPort" : 8081, "protocol" : "tcp" } }, "registration" : { "service/http" : { "ports" : { "http" : { } } } }, "registrationDomain" : "", "volumes" : { "/path/to/mysecretconfig.yaml:ro:ro" : "/path/to/mysecretconfig.yaml" } }
@version $Revision: 1.17 $ $ $Date: 2008/04/11 11:21:00 $ @author Kay Ramme @see com.sun.star.lib.uno.environments.remote.ThreadID @see com.sun.star.lib.uno.environments.remote.IReceiver @since UDK1.0
Every time it "runs", it will be recorded as a {@link Run} object.
To create a custom job type, extend {@link TopLevelItemDescriptor} and put {@link Extension} on it. @author Kohsuke Kawaguchi
CreateData classes found in the database subdirectories.
@author Jim Menard, jimm@io.com
The unit of computation in the resource manager.
| Responsibilities | Collaborations |
|---|---|
| Aggregate many coninuations together into a single continuation. | |
| Sequentially process aggregated continuations. | {@link Event} |
| Provide running and completion status of the aggregate continuation. | |
| Execute a terminal continuation upon job completion. | {@link JobCompletionHandler} |
Jobs have a state that indicates what they are currently doing. When constructed, jobs start with a state value of NONE. When a job is scheduled to be run, it moves into the WAITING state. When a job starts running, it moves into the RUNNING state. When execution finishes (either normally or through cancelation), the state changes back to NONE.
A job can also be in the SLEEPING state. This happens if a user calls Job.sleep() on a waiting job, or if a job is scheduled to run after a specified delay. Only jobs in the WAITING state can be put to sleep. Sleeping jobs can be woken at any time using Job.wakeUp(), which will put the job back into the WAITING state.
Jobs can be assigned a priority that is used as a hint about how the job should be scheduled. There is no guarantee that jobs of one priority will be run before all jobs of lower priority. The javadoc for the various priority constants provide more detail about what each priority means. By default, jobs start in the LONG priority class.
@see IJobManager
@since 3.0
Note: once the scheduler engine processes a job run, it will create a new {@link IJobResult}, which will contain full historical information about job runs. {@link Job} will contain only minimal of such temporal information. @author aphillips
The interface to be implemented by classes which represent a 'job' to be performed.
Instances of Job must have a public no-argument constructor.
JobDataMap provides a mechanism for 'instance member data' that may be required by some implementations of this interface.
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |