public abstract class AbstractScheduledLockedJob
extends org.springframework.scheduling.quartz.QuartzJobBean
JobLockService
. It makes the
cluster aware locking of the job transparent to the implementation. On the
job's spring JobExecutionContext
it
will still always have to be passed as parameter the
jobLockService
. The name to be
used for locking of the job is optional, if none is passed a name will be
composed using the simple name of the implementation class. In general if it
may make sense to have more than one job setup using the same class you
should always use a different name on each
JobExecutionContext
to differentiate
the jobs, unless you want the lock to be shared between the different instances.
The only method to be implemented when extending this class is executeJob(JobExecutionContext)
.Constructor and Description |
---|
AbstractScheduledLockedJob() |
Modifier and Type | Method and Description |
---|---|
protected void |
executeInternal(org.quartz.JobExecutionContext jobContext) |
abstract void |
executeJob(org.quartz.JobExecutionContext jobContext)
This is the method that should be implemented by any extension of the
abstract class.
|
protected final void executeInternal(org.quartz.JobExecutionContext jobContext) throws org.quartz.JobExecutionException
executeInternal
in class org.springframework.scheduling.quartz.QuartzJobBean
org.quartz.JobExecutionException
public abstract void executeJob(org.quartz.JobExecutionContext jobContext) throws org.quartz.JobExecutionException
jobContext
- context of the execution for retrieving services, etcorg.quartz.JobExecutionException
- if a job fails to executeCopyright © 2005–2017 Alfresco Software. All rights reserved.