Examples of JobExecutor

com.asakusafw.testdriver.JobExecutor
Executes a job.
com.thenetcircle.comsumerdispatcher.job.JobExecutor
org.activiti.engine.impl.jobexecutor.JobExecutor

Interface to the work management component of activiti.

This component is responsible for performing all background work ( {@link Job Jobs}) scheduled by activiti.

You should generally only have one of these per Activiti instance (process engine) in a JVM. In clustered situations, you can have multiple of these running against the same queue + pending job list.
@author Daniel Meyer @author Joram Barrez
org.apache.sling.event.jobs.consumer.JobExecutor
A job executor consumes a job. A job executor registers itself with the {@link #PROPERTY_TOPICS} service registrationproperty. The value of this property defines which topics an executor is able to process. Each string value of this property is either a job topic or a topic category ending with "/*" which means all topics in this category. For example, the value "org/apache/sling/jobs/*" matches the topics "org/apache/sling/jobs/a" and "org/apache/sling/jobs/b" but neither "org/apache/sling/jobs" nor "org/apache/sling/jobs/subcategory/a" If there is more than one job executor or consumer registered for a job topic, the selection is as follows: - If there is a single consumer registering for the exact topic, this one is used - If there is more than a single consumer registering for the exact topic, the one with the highest service ranking is used. If the ranking is equal, the one with the lowest service ID is used. - If there is a single consumer registered for the category, it is used - If there is more than a single consumer registered for the category, the service with the highest service ranking is used. If the ranking is equal, the one with the lowest service ID is used. If the executor decides to process the job asynchronously, the processing must finish within the current lifetime of the job executor. If the executor (or the instance of the executor) dies, the job processing will mark this processing as failed and reschedule. @since 1.1
org.camunda.bpm.engine.impl.jobexecutor.JobExecutor

Interface to the component responsible for performing background work ( {@link Job Jobs}).

The {@link JobExecutor} is capable of dispatching to multiple process engines,ie. multiple process engines can share a single Thread Pool for performing Background Work.

In clustered situations, you can have multiple Job Executors running against the same queue + pending job list.
@author Daniel Meyer
org.jbpm.job.executor.JobExecutor
org.jbpm.pvm.internal.jobexecutor.JobExecutor
manager for job execution threads and their configuration. @author Tom Baeyens, Guillaume Porcher

Examples of org.jbpm.pvm.internal.jobexecutor.JobExecutor

      
      // release the lock on the timer
      release();
      
      // notify the jobExecutor at the end of the transaction
      JobExecutor jobExecutor = environment.get(JobExecutor.class);
      if (jobExecutor!=null) {
        Transaction transaction = environment.get(Transaction.class);
        if (transaction==null) {
          throw new JbpmException("no transaction in environment");
        }

View Full Code Here

Examples of org.jbpm.pvm.internal.jobexecutor.JobExecutor

  public JobExecutorDescriptor() {
    super(JobExecutor.class.getName());
  }


  public Object construct(WireContext wireContext) {
    JobExecutor jobExecutor = (JobExecutor) super.construct(wireContext);
    if (autoStart) {
      wireContext.addListener(new JobExecutorStopper(jobExecutor));
    }
    return jobExecutor;
  }

View Full Code Here

0 1 2 3 4 5

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.