精品乱码一区二区三区四区,亚洲精品国产综合区久久久久久久,岛国av一区二区三区

spring��d��调度�Ҏ(gu��)��之Quartz

�C�物 — Tue, 02 Nov 2010 00:52:00 GMT

摘要: 一、Quartz��? Quartz是一个开放源码项目，专注于�Q务调度器�Q�提供了极�ؓ(f��)�q�泛的特性如持久化�Q务，集群和分布式��d��{�。Spring对Quartz的集成与其对JDK Timer的集成在��d��、触发器和调度计划的声明式配�|�方面等都非常相伹{�� ?Quartz的核心由两个接口和两个类�l�成�Q�Job和Scheduler接口�Q�JobDetail... 阅读全文

�C�物 2010-11-02 08:52 发表评论

Spring JMS

�C�物 — Wed, 01 Sep 2010 14:33:00 GMT

1 DestinationResolver
DestinationResolver接口的作用是��指定的目的地名解析为目的地实例。其定义如下�Q?/p>

Java代码

public interface DestinationResolver {
Destination resolveDestinationName(Session session, String destinationName,
boolean pubSubDomain) throws JMSException;
}

参数pubSubDomain用于指定是��用“发�?订阅”模式（解析后的目的地是Topic�Q�，�q�是使用“点对点”模式（解析后的目的地是Queue�Q��?/p>

CachingDestinationResolver接口�l�承了DestinationResolver�Q�增加了�~�存的功能，其接口定义如下：(x��)

Java代码

public interface CachingDestinationResolver extends DestinationResolver {
void removeFromCache(String destinationName);
void clearCache();
}

在目的地失效的时候，removeFromCache�Ҏ(gu��)��?x��)被调用�Q�在JMS provider失效的时候，clearCache�Ҏ(gu��)��?x��)被调用�?br />
1.1 DynamicDestinationResolver
DynamicDestinationResolver实现了DestinationResolver接口。根据指定的目的地名�Q�DynamicDestinationResolver�?x��)动态创建目的地实例。针对JMS1.1规范�Q�它采用如下�Ҏ(gu��)��创徏目的圎ͼ�(x��)

Java代码

session.createTopic(topicName)
session.createQueue(queueName);

1.2 JndiDestinationResolver
JndiDestinationResolver�l�承自JndiLocatorSupport�Q? 同时实现了CachingDestinationResolver接口。如果在JMS provider中配�|�了静态目的地�Q�那么JndiDestinationResolver通过JNDI查找的方式获得目的地实例�?/p>

JndiDestinationResolver的fallbackToDynamicDestination属性用于指定在JNDI查找��p�|后，是否�? 用动态目的地�Q�默认值是false。JndiDestinationResolver的cache属性用于指定是否对目的地实例进行缓存，默认值是 true�?/p>

1.3 BeanFactoryDestinationResolver
BeanFactoryDestinationResolver实现了DestinationResolver接口和BeanFactoryAware接口。它�?x��)根据指定的目的地名从BeanFactory中查扄��的地实例。以下是相关的代码：(x��)

Java代码

public Destination resolveDestinationName(Session session, String destinationName,
boolean pubSubDomain) throws JMSException {
Assert.state(this.beanFactory != null, "BeanFactory is required");
try {
return (Destination) this.beanFactory.getBean(destinationName, Destination.class);
}
catch (BeansException ex) {
throw new DestinationResolutionException(
"Failed to look up Destinaton bean with name '" + destinationName + "'", ex);
}
}

2 JmsAccessor
抽象�c�JmsAccessor是JmsTemplate、SimpleMessageListenerContainer�? DefaultMessageListenerContainer�{�concrete class的基�c�R��JmsAccessor定义了如下几个用于访问JMS服务的共通属性�?/p>

Java代码

private ConnectionFactory connectionFactory;
private boolean sessionTransacted = false ;
private int sessionAcknowledgeMode = Session.AUTO_ACKNOWLEDGE;

JmsAccessor提供了创建Connection和Session的方法，如下�Q?/p>

Java代码

protected Connection createConnection() throws JMSException {
return getConnectionFactory().createConnection();
}
protected Session createSession(Connection con) throws JMSException {
return con.createSession(isSessionTransacted(), getSessionAcknowledgeMode());
}

2.1 JmsDestinationAccessor
抽象�c�JmsDestinationAccessor�l�承自JmsAccessor�Q�增加了destinationResolver�? pubSubDomain属性。destinationResolver的默认值是DynamicDestinationResolver的实例，也就�? 说默认采用动态目的地解析的方式；pubSubDomain用于指定是��用“发�?订阅”模式还是��用“点对点”模式，默认值是false�?br />
JmsDestinationAccessor提供了用于解析目的地的方法，如下�Q?/p>

Java代码

protected Destination resolveDestinationName(Session session, String destinationName)
throws JMSException {
return getDestinationResolver().resolveDestinationName(session, destinationName,
isPubSubDomain());
}

2.2 AbstractJmsListeningContainer
AbstractJmsListeningContainer�l�承自JmsDestinationAccessor�Q�作为所有Message Listener Container的公共基�c�R��它主要提供了JMS connection的生命周期管理的功能�Q�但是没有对消息接收的方式（��d��接收方式或者异步接收方式）(j��)�{�做��M��假定。该�c�M��要的属性如下：(x��)

Java代码

private String clientId;
private Connection sharedConnection;

clientId通常用于持久订阅�Q�sharedConnection保存了被�׃�n的JMS connection�?/p>

该类定义了如下的抽象�Ҏ(gu��)��Q�以便子�c�d��以决定是否��用共享的JMS connection�?/p>

Java代码

protected abstract boolean sharedConnectionEnabled();

2.3 AbstractMessageListenerContainer
AbstractMessageListenerContainer�l�承自AbstractJmsListeningContainer�Q�也是作为所有Message Listener Container的公共基�c�R��该�c�M��要的属性如下：(x��)

Java代码

private volatile Object destination;
private volatile Object messageListener;
private boolean exposeListenerSession = true ;

destination用于指定接收消息的目的地�?br /> messageListener用于指定处理消息的listener。对于messageListener�Q�它既可以是�W�合JMS规范�? javax.jms.MessageListener�Q�也可以是Spring�Ҏ(gu��)��? org.springframework.jms.listener.SessionAwareMessageListener�? SessionAwareMessageListener的定义如下：(x��)

Java代码

public interface SessionAwareMessageListener {
void onMessage(Message message, Session session) throws JMSException;
}

跟javax.jms.MessageListener相比�Q�这个接口的onMessage�Ҏ(gu��)��增加了一个Session �c�d��的参敎ͼ�可以通过�q�个session发送回复消息（reply message�Q��?/p>

如果使用了SessionAwareMessageListener �c�d��的message listener�Q�那么exposeListenerSession参数指定了传入onMessage�Ҏ(gu��)��的session参数是否是创��Z�� MessageConsumer的session�Q�默认值是true。如果是false�Q�那�? AbstractMessageListenerContainer�?x��)在connection上新��Z��个session�Q��ƈ传入onMessage�Ҏ(gu��)��?br />
2.4 AbstractPollingMessageListenerContainer
AbstractPollingMessageListenerContainer�l�承自AbstractMessageListenerContainer�Q�它提供了对于主动接收消�?polling)的支持，以及(qi��ng)支持外部的事务管理�?/p>

Java代码

private boolean pubSubNoLocal = false ;
private long receiveTimeout = DEFAULT_RECEIVE_TIMEOUT;
private PlatformTransactionManager transactionManager;

如果使用“发�?订阅”模式，那么pubSubNoLocal 属性指定通过某个�q�接发送到某个Topic的消息，是否应该被投递回�q�个�q�接�?/p>

receiveTimeout属性用于指定调用MessageConsumer的receive�Ҏ(gu��)��时的��时旉��Q�默认值是1�U�。需要注意的是，�q�个值应该比transactionManager 中指定的事务��时旉��略小�?/p>

通常情况下，应该为transactionManager讄��一�? org.springframework.transaction.jta.JtaTransactionManager的实例，此外也要讄��一个支�? XA的ConnectionFactory。需要注意的是，XA 事务�Ҏ(gu��)��能有较大的影响�?br /> 如果只是希望使用local JMS transaction�Q�那么只要设�|�sessionTransacted为true或者��用JmsTransactionManager卛_��。实际上�Q? 如果讄��了非JTA的transactionManager�Q�那么sessionTransacted属性会(x��)自动被设�|�成true�?br /> �׃��local JMS transaction无法同其它local transaction�Q�例如local database transaction�Q�进行协调，因此客户端程序可能需要对重发的消息进行检查。JMS规范要求�Q�JMS provider应该��重发消息的JMSRedelivered属性设�|��ؓ(f��)true�?br />
2.5 SimpleMessageListenerContainer
SimpleMessageListenerContainer�l�承自AbstractMessageListenerContainer�Q��用异步方�? 接收消息�Q�也��是通过MessageConsumer上注册MessageListener的方式接收消息）(j��)。该�c�M��要的属性如下：(x��)

Java代码

private boolean pubSubNoLocal = false ;
private int concurrentConsumers = 1 ;
private Set sessions;
private Set consumers;
private TaskExecutor taskExecutor;

如果使用“发�?订阅”模式，那么pubSubNoLocal 属性指定通过某个�q�接发送到某个Topic的消息，是否应该被投递回�q�个�q�接�?/p>

SimpleMessageListenerContainer允许创徏多个Session和MessageConsumer来接收消息。具体的个数�? concurrentConsumers属性指定。需要注意的是，应该只是在Destination为Queue的时候才使用多个 MessageConsumer�Q�Queue中的一个消息只能被一个Consumer接收�Q�，虽然使用多个MessageConsumer�?x��)提高消息处�? 的性能�Q�但是消息处理的��序却得不到保证�Q�消息被接收的顺序仍然是消息发送时的顺序，但是�׃��消息可能�?x��)被�q�发处理�Q�因此消息处理的��序可能和消息发送的 ��序不同。此外，不应该在Destination为Topic的时候��用多个MessageConsumer�Q�这是因为多�? MessageConsumer�?x��)接收到同样的消息�?/p>

SimpleMessageListenerContainer创徏的Session和MessageConsumer分别保存在sessions和consumers属性中�?/p>

taskExecutor属性的默认值是null�Q�也��是��_(d��)��对MessageListener�Q�或�? SessionAwareMessageListener�Q�的回调是在MessageConsumer的内部线�E�中执行。如果指定了 taskExecutor�Q�那么回调是在TaskExecutor内部的线�E�中执行。以下是相关的代码：(x��)

Java代码

protected MessageConsumer createListenerConsumer( final Session session)
throws JMSException {
Destination destination = getDestination();
if (destination == null) {
destination = resolveDestinationName(session, getDestinationName());
}
MessageConsumer consumer = createConsumer(session, destination);
if (this.taskExecutor != null) {
consumer.setMessageListener(new MessageListener() {
public void onMessage(final Message message) {
taskExecutor.execute(new Runnable() {
public void run() {
processMessage(message, session);
}
});
}
});
}
else {
consumer.setMessageListener(new MessageListener() {
public void onMessage(Message message) {
processMessage(message, session);
}
});
}
return consumer;
}

需要注意的是，如果指定了taskExecutor�Q�那么消息在被taskExecutor内部的线�E�处理前�Q�可能已�l�被��认�q�了�Q�外层的 onMessage�Ҏ(gu��)��可能已经执行�l�束了）(j��)。因此如果��用事务Session或者Session.CLIENT_ACKNOWLEDGE�c�d��的确认模式，那么可能�?x��)导致问题�?/p>

该类的sharedConnectionEnabled�Ҏ(gu��)��Q�在AbstractJmsListeningContainer中定义）(j��)��L��q�回true�Q? 因此SimpleMessageListenerContainer�?x��)��用共享的JMS connection�?br />
2.6 DefaultMessageListenerContainer
DefaultMessageListenerContainer�l�承�? AbstractPollingMessageListenerContainer�Q�主要��用同步的方式接收消息�Q�也��是通过循环调用 MessageConsumer.receive的方式接收消息）(j��)。该�c�M��要的属性如下：(x��)

Java代码

private int concurrentConsumers = 1 ;
private int maxConcurrentConsumers = 1 ;
private int maxMessagesPerTask = Integer.MIN_VALUE;
private int idleTaskExecutionLimit = 1 ;
private final Set scheduledInvokers = new HashSet();
private TaskExecutor taskExecutor;
private int cacheLevel = CACHE_AUTO;

跟SimpleMessageListenerContainer一��P��DefaultMessageListenerContainer也支持创建多�? Session和MessageConsumer来接收消息。跟SimpleMessageListenerContainer不同�? 是，DefaultMessageListenerContainer创徏了concurrentConsumers所指定个数�? AsyncMessageListenerInvoker�Q�实��C��SchedulingAwareRunnable接口�Q�，�q�交�l? taskExecutor�q�行�?/p>

maxMessagesPerTask属性的默认值是Integer.MIN_VALUE�Q�但是如果设�|�的taskExecutor�Q�默认值是 SimpleAsyncTaskExecutor�Q�实��C��SchedulingTaskExecutor接口�q�且�? prefersShortLivedTasks�Ҏ(gu��)��q�回true�Q�也��是说该TaskExecutor們֐�于短期�Q务）(j��)�Q�那�? maxMessagesPerTask属性会(x��)自动被设�|��ؓ(f��)10�?br /> 如果maxMessagesPerTask属性的值小�?�Q�那么AsyncMessageListenerInvoker.run�Ҏ(gu��)��?x��)在循环中反复尝�? 接收消息�Q��ƈ在接收到消息后调用MessageListener�Q�或者SessionAwareMessageListener�Q�；如果 maxMessagesPerTask属性的��g��于0�Q�那么AsyncMessageListenerInvoker.run�Ҏ(gu��)��里最多会(x��)��试接收消息 maxMessagesPerTask�ơ，每次接收消息的超时时间由其父�c? AbstractPollingMessageListenerContainer的receiveTimeout属性指定。如果在�q�些��试中都没有接收到消息，那么AsyncMessageListenerInvoker的idleTaskExecutionCount属性会(x��)被篏加。在run�Ҏ(gu��)��执行�? 毕前�?x��)对idleTaskExecutionCount�q�行��(g��)查，如果该��D��q�了 DefaultMessageListenerContainer.idleTaskExecutionLimit�Q�默认�?�Q�，那么�q�个 AsyncMessageListenerInvoker可能�?x��)被销毁�?/p>

所有AsyncMessageListenerInvoker实例都保存在scheduledInvokers中，实例的个数可以在 concurrentConsumers和maxConcurrentConsumers之间��动。跟 SimpleMessageListenerContainer一��P��应该只是在Destination为Queue的时候才使用多个 AsyncMessageListenerInvoker实例�?/p>

cacheLevel属性用于指定是否对JMS资源�q�行�~�存�Q�可选的值是CACHE_NONE = 0、CACHE_CONNECTION = 1、CACHE_SESSION = 2、CACHE_CONSUMER = 3和CACHE_AUTO = 4。默认情况下�Q�如果transactionManager属性不为null�Q�那么cacheLevel被自动设�|��ؓ(f��)CACHE_NONE�Q�不�q�行�~? 存）(j��)�Q�否则cacheLevel被自动设�|��ؓ(f��)CACHE_CONSUMER�?/p>

如果cacheLevel属性值大于等于CACHE_CONNECTION�Q�那么sharedConnectionEnabled�Ҏ(gu��)��Q�在AbstractJmsListeningContainer中定义）(j��)�q�回true�Q�也��是说��用共享的JMS�q�接�?/p>

3 SingleConnectionFactory
SingleConnectionFactory实现了ConnectionFactory接口�Q�其createConnection�Ҏ(gu��)��L��q�回相同�? Connection。可以在SingleConnectionFactory的构造函��C��传入Connection对象或�? ConnectionFactory对象�Q�用来创��代理的连接对象�? SingleConnectionFactory.createConnection�Ҏ(gu��)��q�回的连接是个代理，它忽略了对stop和close�Ҏ(gu��)��的调�? �Q�连接会(x��)在SingleConnectionFactory.destroy�Ҏ(gu��)��中关闭）(j��)�?/p>

SingleConnectionFactory的reconnectOnException属性用来指定是否在�q�接抛出JMSException的时候，对连接进行重�|�，重置后如果再调用createConnection�Ҏ(gu��)��Q�那么会(x��)�q�回一个新的连接�?/p>

需要注意的是，AbstractJmsListeningContainer�cȝ��抽象�Ҏ(gu��)��sharedConnectionEnabled指定了是否在 message listener container内部使用�׃�n的JMS�q�接。因此通常情况下不需要�ؓ(f��)单独的message listener container讄��SingleConnectionFactory�Q�及(qi��ng)其子�c�）(j��)�Q�如果希望在不同的message listener container之间�׃�nJMS�q�接�Q�那么可以考虑使用SingleConnectionFactory�?br />
3.1 CachingConnectionFactory
CachingConnectionFactory�l�承自SingleConnectionFactory�Q�增加了对Session和MessageProducer�~�存的功能。该�c�M��要的属性如下：(x��)

Java代码

private int sessionCacheSize = 1 ;
private boolean cacheProducers = true ;

sessionCacheSize属性指定了被缓存的Session实例的个敎ͼ�默认值是1�Q�，也就是说�Q�如果同时请求的Session个数大于sessionCacheSize�Q�那么这些Session不会(x��)被缓存，而是正常的被创徏和销毁�?/p>

cacheProducers属性指定了是否对MessageProducer�q�行�~�存�Q�默认值是true�?/p>

�C�物 2010-09-01 22:33 发表评论

�C�物 — Tue, 07 Apr 2009 01:29:00 GMT

摘要: 前段旉��对Spring的事务配�|�做了比较深入的研究�Q�在此之间对Spring的事务配�|�虽说也配置�q�，但是一直没有一个清楚的认识。通过�q�次的学�?f��n)发觉Spring的事务配�|�只要把思�\理清�Q�还是比较好掌握的�? �ȝ��如下�Q? Spring配置文�g中关于事务配�|��L��׃��个组成部分，分别是DataSource、TransactionM... 阅读全文

�C�物 2009-04-07 09:29 发表评论

(转蝲)Spring Security 2 配置�_�讲

�C�物 — Wed, 25 Feb 2009 11:15:00 GMT

摘要: 论坛上看了不��Spring Security的相��x��章。这些文章基本上都还是基于Acegi-1.X的配�|�方式，而主要的配置�C�Z��也来自于SpringSide的�A(ch��)献�? 众所周知�Q�Spring Security针对Acegi的一个重大的改进��在于其配置方式大大��化了。所以如果配�|�还是基于Acegi-1.X�q�样比较�J�琐的配�|�方式的话，那么我们�q�不如直接��用Acegi而不要去升��了。所以在�q�里�Q�我... 阅读全文

�C�物 2009-02-25 19:15 发表评论

Spring Security学习(f��n)�ȝ��一

�C�物 — Mon, 23 Feb 2009 12:26:00 GMT

摘要: 在认识Spring Security之前�Q�所有的权限验证逻辑都�؜杂在业务逻辑中，用户的每个操作以前可能都需要对用户是否有进行该��Ҏ(gu��)��作的权限�q�行判断�Q�来辑ֈ�认证授权�?目的。类��D��L(f��ng)��权限验证逻辑代码被分散在�pȝ��的许多地方，难以�l�护。AOP�Q�Aspect Oriented Programming�Q�和Spring Security为我们的应用�E�序很好的解决了此类问题�Q�正如系�l�日志，事务��理�{�这... 阅读全文

�C�物 2009-02-23 20:26 发表评论

Spring2事务��理的两�U�配�|?XML&&标注)-转蝲

�C�物 — Thu, 16 Oct 2008 12:04:00 GMT

摘要: package com.epeer.dao; public interface UserDao { public void insertUserIp(String startip, String endip); } package&nbs... 阅读全文

�C�物 2008-10-16 20:04 发表评论

Spring--��单��用quartz实现定时作业

�C�物 — Sat, 17 May 2008 15:29:00 GMT

"1.0" encoding="UTF-8"?>
"-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
"z" class="org.springframework.scheduling.quartz.SchedulerFactoryBean">
"triggers">
"cronReportTrigger"/>
"courseService" class="com.spring.helloworld.CourseService">
"cronReportTrigger"
class="org.springframework.scheduling.quartz.CronTriggerBean">
"jobDetail">"scheduledReportJobDetail"/>
"cronExpression">10,15,20,25,30,35,40,45,50,55 * * * * ?

package com.spring.helloworld;
import java.io.FileNotFoundException;
import org.springframework.beans.BeansException;
import org.springframework.beans.factory.BeanFactory;
import org.springframework.beans.factory.xml.XmlBeanFactory;
import org.springframework.core.io.FileSystemResource;
import com.spring.hellow.LogInit;
import com.spring.hellow.QuestException;
public class TaskApp {
public static void main(String[] args) throws BeansException, FileNotFoundException, QuestException, InterruptedException {
new LogInit("WEB-INF/classes/com/spring/helloworld/log4j.properties");
BeanFactory factory = new XmlBeanFactory(new FileSystemResource(
"WEB-INF/classes/" +
"com/spring/helloworld/" +
"helloworld.xml"));
factory.getBean("z");//��Z��么必��ȝ��q�个�Ҏ(gu��)��触发呢不触发��Z��么不行呢?
}
}

附：(x��)cronExpression配置说明

字段	允许�?/th>	允许的特�D�字�W?/th>
`�U?/code>`	`0-59`	`, - * /`
`�?/code>`	`0-59`	`, - * /`
`��时`	`0-23`	`, - * /`
`日期`	`1-31`	`, - * ? / L W C`
`月䆾`	`1-12 或�?JAN-DEC`	`, - * /`
`星期`	`1-7 或�?SUN-SAT`	`, - * ? / L C #`
`�q�_(d��)��可选）(j��)`	`留空, 1970-2099`	`, - * /`

字段	允许�?/th>	允许的特�D�字�W?/th>
`�U?/code>`	`0-59`	`, - * /`
`�?/code>`	`0-59`	`, - * /`
`��时`	`0-23`	`, - * /`
`日期`	`1-31`	`, - * ? / L W C`
`月䆾`	`1-12 或�?JAN-DEC`	`, - * /`
`星期`	`1-7 或�?SUN-SAT`	`, - * ? / L C #`
`�q�_(d��)��可选）(j��)`	`留空, 1970-2099`	`, - * /`

The '*' character is used to specify all values. For example, "*" in the minute field means "every minute".
“*”字符被用来指定所有的倹{��如�Q?#8221;*“在分钟的字段域里表示“每分�?#8221;�?
The '?' character is allowed for the day-of-month and day-of-week fields. It is used to specify 'no specific value'. This is useful when you need to specify something in one of the two fileds, but not the other. See the examples below for clarification.
“?”字符只在日期域和星期域中使用。它被用来指�?#8220;非明��的�?#8221;。当你需要通过在这两个域中的一个来指定一些东西的时候，它是有用的。看下面的例子你��׃��(x��)明白�?
月䆾中的日期和星期中的日期这两个元素时互斥的一起应该通过讄��一个问�??)来表明不惌��|�那个字�D?br />
The '-' character is used to specify ranges For example "10-12" in the hour field means "the hours 10, 11 and 12".
“-”字符被用来指定一个范围。如�Q?#8220;10-12”在小时域意味着“10炏V�?1炏V�?2�?#8221;�?

The ',' character is used to specify additional values. For example "MON,WED,FRI" in the day-of-week field means "the days Monday, Wednesday, and Friday".
“,”字符被用来指定另外的倹{��如�Q?#8220;MON,WED,FRI”在星期域里表�C?#8221;星期一、星期三、星期五”.

The '/' character is used to specify increments. For example "0/15" in the seconds field means "the seconds 0, 15, 30, and 45". And "5/15" in the seconds field means "the seconds 5, 20, 35, and 50". Specifying '*' before the '/' is equivalent to specifying 0 is the value to start with. Essentially, for each field in the expression, there is a set of numbers that can be turned on or off. For seconds and minutes, the numbers range from 0 to 59. For hours 0 to 23, for days of the month 0 to 31, and for months 1 to 12. The "/" character simply helps you turn on every "nth" value in the given set. Thus "7/6" in the month field only turns on month "7", it does NOT mean every 6th month, please note that subtlety.

The 'L' character is allowed for the day-of-month and day-of-week fields. This character is short-hand for "last", but it has different meaning in each of the two fields. For example, the value "L" in the day-of-month field means "the last day of the month" - day 31 for January, day 28 for February on non-leap years. If used in the day-of-week field by itself, it simply means "7" or "SAT". But if used in the day-of-week field after another value, it means "the last xxx day of the month" - for example "6L" means "the last friday of the month". When using the 'L' option, it is important not to specify lists, or ranges of values, as you'll get confusing results.

L�?#8216;last’的省略写法可以表�C�day-of-month和day-of-week域，但在两个字段中的意思不同，例如day-of-month域中表示一个月的最后一天，
如果在day-of-week域表�C?#8216;7’或�?#8216;SAT’�Q�如果在day-of-week域中前面加上数字�Q�它表示一个月的最后几天，例如‘6L’��p��C�Z��个月的最后一�?br /> 星期五，

The 'W' character is allowed for the day-of-month field. This character is used to specify the weekday (Monday-Friday) nearest the given day. As an example, if you were to specify "15W" as the value for the day-of-month field, the meaning is: "the nearest weekday to the 15th of the month". So if the 15th is a Saturday, the trigger will fire on Friday the 14th. If the 15th is a Sunday, the trigger will fire on Monday the 16th. If the 15th is a Tuesday, then it will fire on Tuesday the 15th. However if you specify "1W" as the value for day-of-month, and the 1st is a Saturday, the trigger will fire on Monday the 3rd, as it will not 'jump' over the boundary of a month's days. The 'W' character can only be specified when the day-of-month is a single day, not a range or list of days
.
The 'L' and 'W' characters can also be combined for the day-of-month expression to yield 'LW', which translates to "last weekday of the month".

The '#' character is allowed for the day-of-week field. This character is used to specify "the nth" XXX day of the month. For example, the value of "6#3" in the day-of-week field means the third Friday of the month (day 6 = Friday and "#3" = the 3rd one in the month). Other examples: "2#1" = the first Monday of the month and "4#5" = the fifth Wednesday of the month. Note that if you specify "#5" and there is not 5 of the given day-of-week in the month, then no firing will occur that month.

The 'C' character is allowed for the day-of-month and day-of-week fields. This character is short-hand for "calendar". This means values are calculated against the associated calendar, if any. If no calendar is associated, then it is equivalent to having an all-inclusive calendar. A value of "5C" in the day-of-month field means "the first day included by the calendar on or after the 5th". A value of "1C" in the day-of-week field means "the first day included by the calendar on or after sunday".
关于cronExpression的介�l?

字段允许�?允许的特�D�字�W?
�U?0-59 , - * /
�?0-59 , - * /
��时 0-23 , - * /
日期 1-31 , - * ? / L W C
月䆾 1-12 或�?JAN-DEC , - * /
星期 1-7 或�?SUN-SAT , - * ? / L C #
�q�_(d��)��可选）(j��) 留空, 1970-2099 , - * /
表达式意�?
"0 0 12 * * ?" 每天中午12点触�?
"0 15 10 ? * *" 每天上午10:15触发
"0 15 10 * * ?" 每天上午10:15触发
"0 15 10 * * ? *" 每天上午10:15触发
"0 15 10 * * ? 2005" 2005�q�的每天上午10:15触发
"0 * 14 * * ?" 在每天下�?点到下午2:59期间的每1分钟触发
"0 0/5 14 * * ?" 在每天下�?点到下午2:55期间的每5分钟触发
"0 0/5 14,18 * * ?" 在每天下�?点到2:55期间和下�?点到6:55期间的每5分钟触发
"0 0-5 14 * * ?" 在每天下�?点到下午2:05期间的每1分钟触发
"0 10,44 14 ? 3 WED" 每年三月的星期三的下�?:10�?:44触发
"0 15 10 ? * MON-FRI" 周一臛_��五的上午10:15触发
"0 15 10 15 * ?" 每月15日上�?0:15触发
"0 15 10 L * ?" 每月最后一日的上午10:15触发
"0 15 10 ? * 6L" 每月的最后一个星期五上午10:15触发
"0 15 10 ? * 6L 2002-2005" 2002�q�至2005�q�的每月的最后一个星期五上午10:15触发
"0 15 10 ? * 6#3" 每月的第三个星期五上�?0:15触发
每天早上6�?
0 6 * * *
每两个小�?
0 */2 * * *
晚上11点到早上8点之间每两个��时�Q�早上八�?
0 23-7/2�Q? * * *
每个月的4号和每个�C�拜的礼拜一到礼拜三的早�?1�?
0 11 4 * 1-3
1�?日早�?�?
0 4 1 1 *

quartz的高�U�特性不仅如�?
1 数据库存�?
2 集群支持
3 数据库持久化��d��Q�trigger
4 trigger 的停止，�q�行
5 ��d��的�Q意添�?
6 比corntrigger 更详��的��d��安排
7 �U�程的内部数据交�?/p>

�C�物 2008-05-17 23:29 发表评论

精品乱码一区二区三区四区,亚洲精品国产综合区久久久久久久,岛国av一区二区三区

spring��d��调度�Ҏ(gu��)��之Quartz

Spring JMS

(转蝲)Spring Security 2 配置�_�讲

Spring Security学习(f��n)�ȝ��一

Spring2事务���理的两�U�配�|?XML&&标注)-转蝲

Spring--���单��用quartz实现定时作业

Spring2事务��理的两�U�配�|?XML&&标注)-转蝲

Spring--��单��用quartz实现定时作业