Decoupling event producers and event consumers in JEE6 using CDI and JMS

In this post I will share my recent findings about Container Dependency Injection in JEE 6, in particular how to decouple the processing threads of  event producers and event consumers. JEE 6 introduces a very nice dependency injection framework (CDI) that has superb support for the Observer pattern in the form of event broadcasting. An Event in CDI is just a regular POJO: public class MyEvent { String data; Date eventTime; .... } Events can be fired by any class through the use of the Event implementation injected automatically by the container via the @Inject annotation:   public class EventProducer { @Inject @Any Event event; public void doSomething() { MyEvent e=new MyEvent(); e.data="This is a test event"; e.eventTime=new Date(); event.fire(e); } } Observing events is even easier, one just needs to declare a method which takes a parameter with the @Observes annotation:   public class EventConsumer { public void afterMyEvent(@Observes MyEvent event) { // .. Insert event logic here } } CDI will automagically wire EventProducer and EventConsumer, so that when EventProducer fires the event, EventConsumer.afterMyEvent gets called. This is pretty cool, as now EventProducer and EventConsumer can work together without direct knowledge of each other. There is however another, more subtle, form of coupling taking place:  event ...

Date: April, 14 2010
Url: http://www.java.net/blog/jjviana/archive/2010/04/13/decoupling-event-producers-and-consumers-jee6-using-cdi-and-jms

Others News