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 JBM 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 JBoss Messaging 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 JBoss Messaging jars and simply run java org.codehaus.stomp.jms.Main.
JBoss Messaging will shortly be implementing the Stomp protocol directly, so you won't have to use StompConnect to be able to use JBoss Messaging with Stomp clients.