]]>
]]>
本篇技术文章介lSpring AOP的实现?nbsp; 阅读全文
]]>
本篇技术文章将作ؓ(f)Spring入门?
阅读全文
]]>
]]>
说明:
本档的配|经q本人测试，都能正确q行?
q行环境Q?Jdk5.0, Spring-2.5, Spring-modules-0.9Q?ehcache-1.6.0-beta4.jar 阅读全文
]]>
]]>
阅读全文
]]>
其实在Spring官方|站是具体的介l，下面本h对其译成?jin)中?如有译不当之处Q敬请各位指正?nbsp; 阅读全文
]]>
]]>
]]>
按照官方3.0版本开发的说明QSpring 2.5.6会(x)是Spring 2.5分支的最后一个版Q整个开发团队将?x)全力投入?3.0版本的开发工作?.0版的MVC会(x)对Restq行支持?
Spring 3.0 is in progress now! view roadmap click here 阅读全文
]]>
关于LazyLoadException异常Q用过Hibernate O/R Mapping工具的h应该都遇到过Q网上也是有很多解决的方案，其中Spring提供的一个方案就是在web.xml增加一个filter,CZ代码如下:
<filter>
<filter-name>entityManager</filter-name>
<filter-class>org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>entityManagerFilter</filter-name>
<url-pattern>*.action</url-pattern>
</filter-mapping>
<filter-name>entityManager</filter-name>
<filter-class>org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter</filter-class>
</filter>
<filter-mapping>
<filter-name>entityManagerFilter</filter-name>
<url-pattern>*.action</url-pattern>
</filter-mapping>
解决办法有了(jin)Q接下来应该?x)有人好奇?x)q个配置filter后它是如何工作的Q?br /> 下面来分析一下这个功能实现的源代? 不过之前Q比较重要的是了(jin)解，Z?x)出现l(f)azyload exception的异常发生?br />
下面我模拟写?jin)一D代码，q段代码׃(x)发生该异?br /> 注：(x)只是Z(jin)说明Q相关的代码q略了(jin)?br />
@Entity
public class Room {
@Id
@Column(length=32)
private String id;
@Column(length=20)
private code;
@OneToMany(mappedBy="room") //default is use lazy load strategy
private Set desks;
}
@Entity
public class Desk {
@Id
@Column(length=32)
private String id;
@Column(length=20)
private code;
@ManyToOne
private Room root;
}
public class RoomSerivce {
@Transactional(readOnly=true)
public Room getRoomById(String roomId) {
Assert.notBlank(roomId, "room'id is null);
return getDao().findById(roomId);
}
}
public class Room {
@Id
@Column(length=32)
private String id;
@Column(length=20)
private code;
@OneToMany(mappedBy="room") //default is use lazy load strategy
private Set desks;
}
@Entity
public class Desk {
@Id
@Column(length=32)
private String id;
@Column(length=20)
private code;
@ManyToOne
private Room root;
}
public class RoomSerivce {
@Transactional(readOnly=true)
public Room getRoomById(String roomId) {
Assert.notBlank(roomId, "room'id is null);
return getDao().findById(roomId);
}
}
1 public class RoomServiceTest {
2
3 public static void main(String[] args[]) {
4
5 //get service from spring beanfactory
6 RoomService service = SpringContext.getSerivce("roomService");
7 Assert.notNull(service, " roomService bean not exsit");
8
9 Room room = service.getRoomById("1");
10 //here lazy exception throw out
11 Set Desks = room.getDesks();
12 CollectionsUtils.toString(Desks);
13 }
14 }
2
3 public static void main(String[] args[]) {
4
5 //get service from spring beanfactory
6 RoomService service = SpringContext.getSerivce("roomService");
7 Assert.notNull(service, " roomService bean not exsit");
8
9 Room room = service.getRoomById("1");
10 //here lazy exception throw out
11 Set Desks = room.getDesks();
12 CollectionsUtils.toString(Desks);
13 }
14 }
分析q段代码Q我们不隑֏玎ͼ在RoomServiceTestq个试的例子中Q因Z用了(jin)ZAnnotation的声明性事务，所以在RoomSerivce.getRoomByIdҎ(gu)q行l束后，事务已l提交了(jin)。但CZ中Room实体与Desk实例的关pM用的是lazy fetch的策略，此时Room对象中的desks集合q是为空?br /> 当执行到下面两句?q才真正使用到desks集合?
Set Desks = room.getDesks();
CollectionsUtils.toString(Desks);
Hibernate׃(x)Ҏ(gu)原来lazy讑֮的方式，取EntityManagerQ?Ҏ(gu)它从数据库查?Desk实现的数据，q时上面我们已经提到Q事务已l随getRoomByIdҎ(gu)的运行结束提? EntityManager对象也已l关闭。此时再调用 EntityManager操作Q就?x)报EntityManager has been closed 异常(lazy load exception)
ok, 清楚q块Q大家有时可能也猜想C(jin)Springq个解决Ҏ(gu)是怎么处理的了(jin)?br /> Spring的TransactionInterceptor 其就是通过AOP负责拦截着所有针对事务TransactionManager的操?
q样Spring可以针对lazy异常q行拦截?jin)?br />
清楚上面的后Q下面的代码是非常好理解?jin)，来看一下OpenEntityManagerInViewFilter的代?
我加?jin)些注释Q大家很Ҏ(gu)明白:
1 protected void doFilterInternal(
2 HttpServletRequest request, HttpServletResponse response, FilterChain filterChain)
3 throws ServletException, IOException {
4
5 //通过WebApplicationContext,从Web服务中取得context实例后，Ҏ(gu)EntityManagerFactory.classcd
6 //取得EntityManagerFacotry实例
7 EntityManagerFactory emf = lookupEntityManagerFactory(request);
8 boolean participate = false;
9
10 //如果?rn)态方法hasResource已经有EntityManagerFactory实例?jin)，׃用再通过
11 //EntityManagerFactory创徏一个新EntityManger?/span>
12 if (TransactionSynchronizationManager.hasResource(emf)) {
13 // Do not modify the EntityManager: just set the participate flag.
14 participate = true;
15 }
16 else {
17 logger.debug("Opening JPA EntityManager in OpenEntityManagerInViewFilter");
18 try {
19 //通过EntityManagerFactory创徏一个新EntityManger,q过bindResourceҎ(gu)
20 //保存到TransactionSynchronizationManager?br /> 21 //q样Q通TransactionSynchronizationManager的getResourceҎ(gu)取得EntityMangerHolder
22 EntityManager em = createEntityManager(emf);
23 TransactionSynchronizationManager.bindResource(emf, new EntityManagerHolder(em));
24 }
25 catch (PersistenceException ex) {
26 throw new DataAccessResourceFailureException("Could not create JPA EntityManager", ex);
27 }
28 }
29
30 try {
31 filterChain.doFilter(request, response);
32 }
33
34 finally {
35 if (!participate) {
36 //每次hl束后，把EntityManager关闭
37 EntityManagerHolder emHolder = (EntityManagerHolder)
38 TransactionSynchronizationManager.unbindResource(emf);
39 logger.debug("Closing JPA EntityManager in OpenEntityManagerInViewFilter");
40 EntityManagerFactoryUtils.closeEntityManager(emHolder.getEntityManager());
41 }
42 }
43 }
44
2 HttpServletRequest request, HttpServletResponse response, FilterChain filterChain)
3 throws ServletException, IOException {
4
5 //通过WebApplicationContext,从Web服务中取得context实例后，Ҏ(gu)EntityManagerFactory.classcd
6 //取得EntityManagerFacotry实例
7 EntityManagerFactory emf = lookupEntityManagerFactory(request);
8 boolean participate = false;
9
10 //如果?rn)态方法hasResource已经有EntityManagerFactory实例?jin)，׃用再通过
11 //EntityManagerFactory创徏一个新EntityManger?/span>
12 if (TransactionSynchronizationManager.hasResource(emf)) {
13 // Do not modify the EntityManager: just set the participate flag.
14 participate = true;
15 }
16 else {
17 logger.debug("Opening JPA EntityManager in OpenEntityManagerInViewFilter");
18 try {
19 //通过EntityManagerFactory创徏一个新EntityManger,q过bindResourceҎ(gu)
20 //保存到TransactionSynchronizationManager?br /> 21 //q样Q通TransactionSynchronizationManager的getResourceҎ(gu)取得EntityMangerHolder
22 EntityManager em = createEntityManager(emf);
23 TransactionSynchronizationManager.bindResource(emf, new EntityManagerHolder(em));
24 }
25 catch (PersistenceException ex) {
26 throw new DataAccessResourceFailureException("Could not create JPA EntityManager", ex);
27 }
28 }
29
30 try {
31 filterChain.doFilter(request, response);
32 }
33
34 finally {
35 if (!participate) {
36 //每次hl束后，把EntityManager关闭
37 EntityManagerHolder emHolder = (EntityManagerHolder)
38 TransactionSynchronizationManager.unbindResource(emf);
39 logger.debug("Closing JPA EntityManager in OpenEntityManagerInViewFilter");
40 EntityManagerFactoryUtils.closeEntityManager(emHolder.getEntityManager());
41 }
42 }
43 }
44
上面的代码就不用多解释了(jin)Q?到现在已l很清楚知道Spring针对 Hibernate的Lazy问题是怎么解决的?br /> 当然我们可以扩展到除Web服务以外Q来实现解决lazy的问题?我们自己来管理TransactionSynchronizationManager可以了(jin))
当然Spring针对 Hibernate(非JPA的实?原理也是一P只是它针对的SessionFactory,也是由TransactionSynchronizationManager来统一理?br />
最后如果大家如q有不清楚的Q欢q一赯论?br />
Good Luck!
Yours Matthew!
]]>
包括很多新功能，如标题中提到的Restful的支持，q有Servlet3.0的支持等?br /> 大概ȝ?jin)一下，Spring3.0中会(x)包括以下一些新Ҏ(gu)?
- 1. Full scale REST support by means of additions to the Spring MVC API - already pretty detailed, and apparently going to be included in the first milestone release
- 2. Support for Unified EL (as seen in Spring Web Flow) - very likely part of 3.0, but no details given
- 3. Annotation support for declaring factory methods - as above
- 4 .Support for Portlet 2.0 (JSR 286), including resource requests (ResourceServingPortlet) - as above
- 5. "Preparations" for Servlet 3.0 specification - sounded a lot like architectural preparations not visible to the "consumer"
- 6. Something to fill the gap between Spring Web Flow and Spring MVC - that sounded very vague
- 7. Inclusion (probably generalisation) of the repeat, retry and resume semantics provided by Spring Batch - was only hinted at, no details given
- 8. Inclusion of the OXM support provided by Spring WS - sounded pretty definitive, but no details given
- 9. Some kind of site definition language for the web stack - no idea whether this is more than a rumour
- 10. Model-based validation for use both in server and client - as above
下面我们具体介绍一下Restful该特?
刚才我也提到?jin)，Spring3.0是基于其目前提供的Spring MVC框架上引入对Rest的支持，q样使其可以很好的融合到Spring中?br /> 下面有一D代码，大家看了(jin)?x)更有体会(x)?br /> 先看一下如何发布Rest风格的服务接?br />
1 @RequestMapping(value = "/gadgets/{id}",
2 method = RequestMethod.GET)
3 public View getGadget(@PathParam String id) {
4 // 功能是根?id 查询 Gadget对象
5 // q回View对象
6 }
7
看到使用Annotation方式Q代码非常简z。@RequestMapping是对访求的资源进行服务的l定Q?value指定服务的资源\? method是指Rest风格中的CRUD的方法?br />
@PathParam是对资源路么参数的解?它会(x)自动Ҏ(gu)提交的数据格式，解析参数倹{?br />
2 method = RequestMethod.GET)
3 public View getGadget(@PathParam String id) {
4 // 功能是根?id 查询 Gadget对象
5 // q回View对象
6 }
7
下面来看一?strong>RestTemplateQ对Rest服务接口的调?
1 // 使用getForObject执行查询操作
2 // (指定参数提交方式)
3 RestTemplate template = new RestTemplate();
4 Gadget gadget = template.getForObject(
5 "http://www.springify.com/gadgets/{id}",
6 Gadget.class, 1);
7
8 // 使用postForLocation 执行新增操作
9 // (指定参数提交方式,使用Map对象)
10 Map<String, String> params =
11 new HashMap<String, String>();
12 params.put("id", 42);
13 URI uri = template.postForLocation(
14 "http://www.springify.com/gadgets/{id}/features",
15 new Feature("Glows in the dark."), params);
16
17 // 删除操作的演C?/span>
18 template.delete(
19 "http://www.springify.com/gadgets/{id}", someId);
20
21
29
2 // (指定参数提交方式)
3 RestTemplate template = new RestTemplate();
4 Gadget gadget = template.getForObject(
5 "http://www.springify.com/gadgets/{id}",
6 Gadget.class, 1);
7
8 // 使用postForLocation 执行新增操作
9 // (指定参数提交方式,使用Map对象)
10 Map<String, String> params =
11 new HashMap<String, String>();
12 params.put("id", 42);
13 URI uri = template.postForLocation(
14 "http://www.springify.com/gadgets/{id}/features",
15 new Feature("Glows in the dark."), params);
16
17 // 删除操作的演C?/span>
18 template.delete(
19 "http://www.springify.com/gadgets/{id}", someId);
20
21
29
ȝQ可以看C用Rest风格的服务发布，可以Ҏ(gu)务资源进行统一的管理，使用发布的接口更清晰?br />
当然在Spring 3.0 发布之前Q上q的APIQannotation可能?x)有变动Q我们也期待Spring能与我们早日见面?br />
最后，׃本h对Rest技术了(jin)解还不是太深入，也希望大家能多提些意见和?br />
Good Luck!
Yours Matthew!
]]>
]]>
]]>
<endpoint input-channel="inputChannel"
default-output-channel="outputChannel"
handler-ref="helloService"
handler-method="sayHello"/>
<beans:bean id="helloService" class="org.springframework.integration.samples.helloworld.HelloService"/>
default-output-channel="outputChannel"
handler-ref="helloService"
handler-method="sayHello"/>
<beans:bean id="helloService" class="org.springframework.integration.samples.helloworld.HelloService"/>
1 public class HelloService {
2
3 public String sayHello(String name) {
4 return "Hello " + name;
5 }
6 }
2
3 public String sayHello(String name) {
4 return "Hello " + name;
5 }
6 }
上面q个例子演CZ(jin)?HelloService配置成一个MessageEndpointlgQ消息从"inputChannel"队列接收后，
调用HelloService.sayHelloҎ(gu)Q等sayHelloҎ(gu)q回后，Ҏ(gu)default-output-channel="outputChannel"的配|?br /> 把返回的l果保存到message.payload属性后发送给"outputChannel"队列
也可Ҏ(gu)Annotation的方式，配置Ҏ(gu)如下Q?br />
<annotation-driven/>
<message-bus auto-create-channels="true"/>
<context:component-scan base-package="org.springframework.integration.samples.helloworld"/>
<beans:bean id="helloService" class="org.springframework.integration.samples.helloworld.HelloService"/>
<message-bus auto-create-channels="true"/>
<context:component-scan base-package="org.springframework.integration.samples.helloworld"/>
<beans:bean id="helloService" class="org.springframework.integration.samples.helloworld.HelloService"/>
1 @MessageEndpoint(input="inputChannel", defaultOutput="outputChannel")
2 public class HelloService {
3
4 @Handler
5 public String sayHello(String name) {
6 return "Hello " + name;
7 }
8 }
2 public class HelloService {
3
4 @Handler
5 public String sayHello(String name) {
6 return "Hello " + name;
7 }
8 }
讄q发操作属?br /> xml配置Q?br />
<endpoint input-channel="exampleChannel" handler-ref="exampleHandler"/>
<!-- 讄q发讄 core核心(j)U程?nbsp;max最大线E数 queue-capacity 队列最大消息数 keep-alive idleU程生命旉-->
<concurrency core="5" max="25" queue-capacity="20" keep-alive="120"/>
</endpoint>
<!-- 讄q发讄 core核心(j)U程?nbsp;max最大线E数 queue-capacity 队列最大消息数 keep-alive idleU程生命旉-->
<concurrency core="5" max="25" queue-capacity="20" keep-alive="120"/>
</endpoint>
annotation配置
1 @MessageEndpoint(input="fooChannel")
2 @Concurrency(coreSize=5, maxSize=20, queueCapacity=20, keepAliveSeconds=120)
3 public class FooService {
4
5 @Handler
6 public void bar(Foo foo) {
7
8 }
9 }
2 @Concurrency(coreSize=5, maxSize=20, queueCapacity=20, keepAliveSeconds=120)
3 public class FooService {
4
5 @Handler
6 public void bar(Foo foo) {
7
8 }
9 }
下面ȝ一下常见的annotation的用方?br /> @MessageEndpoint
它表C处理消息对象的l端节点。一般与其它的元数据标记一起用?br /> 下面?x)具体介l与该元数据标记一起用的其它标识的用方法?br />
@MessageEndpoint源代码：(x)
1 @Target(ElementType.TYPE)
2 @Retention(RetentionPolicy.RUNTIME)
3 @Inherited
4 @Documented
5 @Component
6 public @interface MessageEndpoint {
7
8 String input() default ""; //接收消息的队列名U?/span>
9 String defaultOutput() default ""; //默认发送消息的队列名称(只有在不讄@Router情况下才有效)
10 int pollPeriod() default 0; //发送消息的轮@旉间隔(只有在不讄@Router情况下才有效)
11 }
2 @Retention(RetentionPolicy.RUNTIME)
3 @Inherited
4 @Documented
5 @Component
6 public @interface MessageEndpoint {
7
8 String input() default ""; //接收消息的队列名U?/span>
9 String defaultOutput() default ""; //默认发送消息的队列名称(只有在不讄@Router情况下才有效)
10 int pollPeriod() default 0; //发送消息的轮@旉间隔(只有在不讄@Router情况下才有效)
11 }
@Handler
消息回调处理的方法。与@MessageEndpoint一起配|?span style="color: red;">(只限M3版，M4以及(qing)后箋版本可以单独使用,具体使用Ҏ(gu)q要{具体的实现出来)Q收到input队列的消息后Q回调@Handler标识的方?br /> 回调Ҏ(gu)的参数类型必Mmessage.payload属性类型相?br /> 注：(x)如果回调Ҏ(gu)有返回? 则回调方法处理完成后Q会(x)返回D|到message.payload属性后Q?br /> 发送消息到@MessageEndpoint的defaultOutput队列。如果defaultOutput没有讑֮Q则抛出异常?br />
@Handler源代码：(x)
1 @Target({ElementType.METHOD, ElementType.ANNOTATION_TYPE})
2 @Retention(RetentionPolicy.RUNTIME)
3 @Inherited
4 @Documented
5 public @interface Handler {
6
7 }
2 @Retention(RetentionPolicy.RUNTIME)
3 @Inherited
4 @Documented
5 public @interface Handler {
6
7 }
下面的例子演CZ(jin)Q从"channel1"队列接收消息后由@Handler标记的方法处理。消息的payload属性值的cd必须与方法的参数cd相同
1 @MessageEndpoint(input="channel1")
2 public class FooService {
3
4 @Handler
5 public void bar(Foo foo) {
6
7 }
8 }
2 public class FooService {
3
4 @Handler
5 public void bar(Foo foo) {
6
7 }
8 }
@Polled
必须与@MessageEndPoint 一起用。但也可以与@Router,@Splitter标识配合使用Q后面再分别举例说明?br /> @Polled 用于开启一个轮循的方式调用Ҏ(gu)的功?br /> 它有三个参数Q?br /> period: 轮@旉间隔(单位:微秒) 默认?1000
initialDelay: 轮@延迟旉(单位:微秒) 默认?
fixedRate: 默认为false
@Polled 源代?br />
1 @Target(ElementType.METHOD)
2 @Retention(RetentionPolicy.RUNTIME)
3 @Inherited
4 @Documented
5 public @interface Polled {
6 int period() default 1000;
7 long initialDelay() default PollingSchedule.DEFAULT_INITIAL_DELAY;
8 boolean fixedRate() default PollingSchedule.DEFAULT_FIXED_RATE;
9
10 }
2 @Retention(RetentionPolicy.RUNTIME)
3 @Inherited
4 @Documented
5 public @interface Polled {
6 int period() default 1000;
7 long initialDelay() default PollingSchedule.DEFAULT_INITIAL_DELAY;
8 boolean fixedRate() default PollingSchedule.DEFAULT_FIXED_RATE;
9
10 }
下面来看几个例子Q?br /> 例子1:
1 @MessageEndpoint(defaultOutput="outputChannel")
2 public class Counter {
3
4 private AtomicInteger count = new AtomicInteger();
5
6 @Polled(period=3000)
7 public int getNumber() {
8 return count.incrementAndGet();
9 }
10 }
2 public class Counter {
3
4 private AtomicInteger count = new AtomicInteger();
5
6 @Polled(period=3000)
7 public int getNumber() {
8 return count.incrementAndGet();
9 }
10 }
q个例子功能是，MessageBus启动后，由@Polled标记 ?U触发getNumberҎ(gu)Q当getNumberҎ(gu)q回后，
把返回D|到message.payload属性后Q发送到outputChannel队列中?br />
例子2:
1 @MessageEndpoint
2 public class Counter {
3
4 private AtomicInteger count = new AtomicInteger();
5
6 @Polled(period=3000)
7 public int getNumber() {
8 return count.incrementAndGet();
9 }
10
11 @Router
12 public String resolveChannel(int i) {
13 if (i % 2 == 0) {
14 return "even";
15 }
16 return "odd";
17 }
18 }
2 public class Counter {
3
4 private AtomicInteger count = new AtomicInteger();
5
6 @Polled(period=3000)
7 public int getNumber() {
8 return count.incrementAndGet();
9 }
10
11 @Router
12 public String resolveChannel(int i) {
13 if (i % 2 == 0) {
14 return "even";
15 }
16 return "odd";
17 }
18 }
q个例子功能是，MessageBus启动后，由@Polled标记 ?U触发getNumberҎ(gu), 当getNumberҎ(gu)q回?
׃resolveChannelҎ(gu)讄?jin)@Router 标识Q则把有getNumberҎ(gu)q回值都?x)传lresolveChannelҎ(gu)Q最?br /> ?x)根据方法的q回?即队列名U? (@Router标记功能)Q把消息发到even队列或是odd队列
注：(x)如果@MessageEndpointcMQ在Ҏ(gu)上标C(jin)@Router标记后，@MessageEndpoint的defaultOutput变成无效了(jin)?/span>
@Splitter
必须与@MessageEndPoint 一起用?br /> 该元数据标识用于分解消息内容Q它所在的Ҏ(gu)的返回值必L一个集?collection).如果集合元素不是Messagecd
但发送时Q自动把集合中的元素对象保存到Message.payload属性后发送。集合中有多个元素Q则?x)发送多次消息?br />
1 @Target(ElementType.METHOD)
2 @Retention(RetentionPolicy.RUNTIME)
3 @Documented
4 @Handler
5 public @interface Splitter {
6 String channel(); //消息发送的队列?/span>
7 }
2 @Retention(RetentionPolicy.RUNTIME)
3 @Documented
4 @Handler
5 public @interface Splitter {
6 String channel(); //消息发送的队列?/span>
7 }
下面两个例子实现效果是一L(fng)
例子1
1 @MessageEndpoint(input="inputChannel")
2 public class HelloService {
3
4 @Splitter(channel="outputChannel")
5 public List<String> sayHello(String name) {
6 String s = "Hello " + name;
7 List<String> list = new ArrayList<String>();
8 list.add(s);
9 return list;
10 }
11 }
12
2 public class HelloService {
3
4 @Splitter(channel="outputChannel")
5 public List<String> sayHello(String name) {
6 String s = "Hello " + name;
7 List<String> list = new ArrayList<String>();
8 list.add(s);
9 return list;
10 }
11 }
12
例子2
1 @MessageEndpoint(input="inputChannel")
2 public class HelloService {
3
4 @Splitter(channel="outputChannel")
5 public List<Message> sayHello(String name) {
6 String s = "Hello " + name;
7 List<Message> list = new ArrayList<Message>();
8 Message message = new GenericMessage<String>(s);
9 list.add(message);
10 return list;
11 }
12 }
2 public class HelloService {
3
4 @Splitter(channel="outputChannel")
5 public List<Message> sayHello(String name) {
6 String s = "Hello " + name;
7 List<Message> list = new ArrayList<Message>();
8 Message message = new GenericMessage<String>(s);
9 list.add(message);
10 return list;
11 }
12 }
@Router
消息队列路由功能?必须与@MessageEndPoint 一起用?br /> 它所在的Ҏ(gu)的返回值类型必LMessageChannle或是String(channel name)cd
具体的例子参考上面?br />
@Publisher
必须与@MessageEndPoint 一起用?br /> 说明Q@Publisher 标识是根?after-returning 切面的AOP 在方面返回值时Q发送消息到指定消息队列 .
下面的例子：(x)说明 fooҎ(gu)调用后，q回g(x)发送到fooChannel消息队列
1 @Publisher(channel="fooChannel")
2 public String foo() {
3 return "bar";
4 }
2 public String foo() {
3 return "bar";
4 }
@Subscriber
必须与@MessageEndPoint 一起用?br /> 接收指定队列的消息内宏V它实现的异步的消息监听事g?br /> 一旦有消息接收刎ͼ则会(x)Ҏ(gu)message.payload g为参敎ͼ回调@Subscriber 标识标记的方?br />
1 @Subscriber(channel="fooChannel")
2 public void log(String foo) {
3 System.out.println(foo);
4 }
2 public void log(String foo) {
3 System.out.println(foo);
4 }
Good Luck!
Yours Matthew!
2008q??4?br />
]]>
]]>
]]>
- XML elements available as of Spring 2.5(Spring2.5 xml标签配置)
- Most commonly used elements(常用的xml标签使用Ҏ(gu))
- NamespacesQ命名空?
- Guide to Spring’s rich set of annotations(Spring支持的annotations技术用指?
官方下蝲地址
下面是官方发布的内容的原?http://www.springframework.org/node/660
DZone has just published a reference card for Spring 2.5 Configuration. The card was written by the very knowledgeable Craig Walls and provides exhaustive details about all the XML configuration options for your Spring 2.5 contexts. It provides a handy desktop reference for any developer building Spring powered applications. XML averse developers should also check out the options in Spring 2.5 for annotation based configuration.
]]>