Chapter 45. Interoperability

45.1. Stomp and StompConnect

Stomp is a wire protocol that allows Stomp clients to communicate with Stomp Brokers. StompConnect is a server that can act as a Stomp broker and proxy the Stomp protocol to the standard JMS API. Consequently, using StompConnect it is possible to turn HornetQ into a Stomp Broker and use any of the available stomp clients. These include clients written in C, C++, c# and .net etc.

To run StompConnect first start the HornetQ server and make sure that it is using JNDI.

Stomp requires the file jndi.properties to be available on the classpath. This should look something like:

java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://localhost:1099
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces

Make sure this file is in the classpath along with the StompConnect jar and the HornetQ jars and simply run java org.codehaus.stomp.jms.Main.

HornetQ will shortly be implementing the Stomp protocol directly, so you won't have to use StompConnect to be able to use HornetQ with Stomp clients.

A list of STOMP clients is available here.

45.2. REST

REST support coming soon!

45.3. AMQP

AMQP support coming soon!