I’ve been doing some work on HornetQ SVN trunk to improve the embeddable HornetQ experience (you’ll see these improvements in the next HornetQ release). You can disagree with me, but I thought that embedding HornetQ was a bit verbose, especially for JMS, so first of all, I wrote two wrapper classes to make this easier. While these classes will be in the next release along with a full docbook explanation, here’s what configuring JMS looks like now:
import org.hornetq.jms.server.embedded.EmbeddedJMS; ... EmbeddedJMS jms = new EmbeddedJMS(); jms.start();
This class will look for hornetq-configuration.xml, hornetq-jms.xml, and hornetq-users.xml within your classpath. It also has the option of manually creating configuration objects via pojo instantiation if you desire (or if you want to wire it with Spring for instance).
Simple Spring Integration
Another thing I did was to provide some simple Spring integration with the HornetQ JMS implementation. I wrote a simple class that extends EmbeddedJMS that will register any configured queues, topics, and ConnectionFactorys direction within the Spring application context so that other beans can reference them. Here’s an example of bootstrapping HornetQ JMS and referencing a queue within a Spring message listener container.
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd"> <bean id="EmbeddedJms" class="org.hornetq.integration.spring.SpringJmsBootstrap" init-method="start" destroy-method="stop"/> <bean id="listener" class="org.hornetq.tests.integration.spring.ExampleListener"/> <bean id="listenerContainer" class="org.springframework.jms.listener.DefaultMessageListenerContainer"> <property name="connectionFactory" ref="ConnectionFactory"/> <property name="destination" ref="/queue/exampleQueue"/> <property name="messageListener" ref="listener"/> </bean> </beans>
Again, this assumes you have configured HornetQ properly within HornetQ specific configuration files. You can also manually declare HornetQ config objects within Spring and inject them into the EmbeddedJMS bean instance too if you don’t want to use HornetQ config files.
Right now, the code does not also register HornetQ objects within JNDI. Do you think I should add this capability? Anyways, I hope you’ll find this HornetQ + Spring integration useful in the next HornetQ release.