Use of tasks for the Spring Task Scheduler (GO)

Article transferred from http://blog.csdn.net/l454822901/article/details/51829307

Recently found that the real bump, spring upgrade to 3 after the original has a Task scheduler, has been using quartz. In fact, it's not quartz bad, just by comparison, using spring task is really a lot easier, whether it's understanding or using.

Spring task provides two ways to configure, as you can imagine, or one is annotation (callout), and the other is XML configuration. But in fact, I feel more awkward here, because the task of scheduling such requirements, usually changes are more, if you use annotation way, the change becomes troublesome, must go to recompile. So, I just chose to configure it in XML, but I still habitually enable labeling, just like the AOP configuration. Annotation method Please find your own @scheduled

The specific configuration can be referenced as follows

XML code

2. <? XML version= "1.0" encoding="UTF-8"?>
4. <beans xmlns="Http://www.springframework.org/schema/beans"
6. xmlns:xsi= "http://www.w3.org/2001/XMLSchema-instance" xmlns:task="http// Www.springframework.org/schema/task "
8. xsi:schemalocation= "
10. Http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
12. Http://www.springframework.org/schema/task http://www.springframework.org/schema/task/spring-task.xsd ">
16. <Bean id= "reminderprocessor" class="Com.foo.task.ReminderProcessor">
18. <property name="Workers">
20. <array value-type="Com.foo.task.Worker">
22. <ref bean="Projectscheduleremindworker" />
24. </Array>
26. </Property>
28. </Bean>
32. <!--Configure Task Linear pool --
34. <task:executor id="executor" pool-size="3" />
36. <task:scheduler id="Scheduler" pool-size="3" />
38. <!--enable annotation mode --
40. <task:annotation-driven scheduler="Scheduler"
42. executor="executor" proxy-target-class="true" />
46. <task:scheduled-tasks scheduler="Scheduler">
48. <task:scheduled ref="reminderprocessor" method="process"
50. cron="0 0 12 * *?" />
52. </task:scheduled-tasks>
54. </Beans>

See the core section

XML code

1. <task:scheduled-tasks scheduler="Scheduler">
2. <task:scheduled ref="reminderprocessor" method="process"
3. cron="0 0 12 * *?" />
4. </task:scheduled-tasks>

This means that the process method in the bean is executed at 12 o ' Reminderprocessor per day. Cron configuration expressions are basically consistent with quartz, but the actual measurements do not support some special characters, such as L,w and z when configuring days, because of the need to perform task scheduling on the third day of the month, but I configure the springtask to report illegal characters.

Therefore, the gap between quartz and springtask is also obvious. Springtask is very simple to use, after all, spring's own, although with quartz can also achieve a combination, but not so simple. and Springtask function is not quartz powerful, quartz cluster and advanced features to go. So you can choose for yourself. But in general, think springtask enough.

Attach a detailed UML description of my example

Use of tasks for the Spring Task Scheduler (GO)