上一篇我已经详细分析了CornTrigger类的源码,类的CronExpression 属性类完成了对定时任务设置的时间进行解析,而在SimpleTrigger类中,有下面SimpleTriggerBean类的源码可知,该类主要完成的工作是设置JobDetail和beanName这两个属性,现在我们主要分下这个类继承 的类SimpleTrigger类。
package org.springframework.scheduling.quartz;
import java.text.ParseException;
import java.util.Date;
import java.util.Map;
import java.util.TimeZone;
import org.quartz.CronTrigger;
import org.quartz.JobDataMap;
import org.quartz.JobDetail;
import org.springframework.beans.factory.BeanNameAware;
import org.springframework.beans.factory.InitializingBean;
import org.springframework.core.Constants;
public class CronTriggerBean extends CronTrigger
implements JobDetailAwareTrigger, BeanNameAware, InitializingBean
{
private static final Constants constants = new Constants(CronTrigger.class);
private JobDetail jobDetail;
private String beanName;
public void setJobDataAsMap(Map jobDataAsMap)
{
getJobDataMap().putAll(jobDataAsMap);
}
public void setMisfireInstructionName(String constantName)
{
setMisfireInstruction(constants.asNumber(constantName).intValue());
}
public void setTriggerListenerNames(String[] names)
{
for (int i = 0; i < names.length; i++)
addTriggerListener(names[i]);
}
public void setJobDetail(JobDetail jobDetail)
{
this.jobDetail = jobDetail;
}
public JobDetail getJobDetail() {
return this.jobDetail;
}
public void setBeanName(String beanName) {
this.beanName = beanName;
}
public void afterPropertiesSet() throws ParseException
{
if (getName() == null) {
setName(this.beanName);
}
if (getGroup() == null) {
setGroup("DEFAULT");
}
if (getStartTime() == null) {
setStartTime(new Date());
}
if (getTimeZone() == null) {
setTimeZone(TimeZone.getDefault());
}
if (this.jobDetail != null) {
setJobName(this.jobDetail.getName());
setJobGroup(this.jobDetail.getGroup());
}
}
}
由于SimpleTrigger类源码多,这里我就只拿出核心代码来分析:
public class SimpleTrigger extends Trigger
{
private static final long serialVersionUID = -3735980074222850397L;
public static final int MISFIRE_INSTRUCTION_FIRE_NOW = 1;
public static final int MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_EXISTING_REPEAT_COUNT = 2;
public static final int MISFIRE_INSTRUCTION_RESCHEDULE_NOW_WITH_REMAINING_REPEAT_COUNT = 3;
public static final int MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_REMAINING_COUNT = 4;
public static final int MISFIRE_INSTRUCTION_RESCHEDULE_NEXT_WITH_EXISTING_COUNT = 5;
public static final int REPEAT_INDEFINITELY = -1;
private static final int YEAR_TO_GIVEUP_SCHEDULING_AT = 2299;
//设置的是跑批开始时间
private Date startTime = null;
//设置的是跑批结束时间
private Date endTime = null;
//设置的是下次跑批日期时间
private Date nextFireTime = null;
//设置的是上一次跑批日期时间
private Date previousFireTime = null;
//设置的是跑批次数
private int repeatCount = 0;
//这里设置的是跑批任务间隔时间,即跑批周期
private long repeatInterval = 0L;
private int timesTriggered = 0;
private boolean complete = false;
//这个函数是更新下次跑批日期时间,猜测是在开始一次跑批的时候机会调用这个函数更新下次跑批日期时间
public void updateWithNewCalendar(Calendar calendar, long misfireThreshold)
{
...
}
//计算首次跑批日期时间 ,这个函数一般在跑批触发器初始化的时候调用。
public Date computeFirstFireTime(Calendar calendar)
{
...
}
此外还有其他一些方法getFireTimeAfter(Date end), getFireTimeBefore(Date end),computeNumTimesFiredBetween(Date start, Date end), Date getFinalFireTime()
等等一些处理方法,这些方法的意义由方法名可知其功能。
以上就是SimpleTrigger类简单的源码分析。
其实对于SimpleTriggerBean和CornTriggerBean的分析一直存在一个问题,在CornTriggerBean源码分析的源码中我也提到了,对这两个对象的使用逻辑。但是究竟是哪个类调用?调用具体逻辑是怎么样的?现在还未可知,这也是接下来呈现给大家的。