Author: jmesnil Date: 2010-04-26 09:27:05 -0400 (Mon, 26 Apr 2010) New Revision: 9165 Modified: trunk/docs/user-manual/en/interoperability.xml Log: doc: moved StompConnect section after native Stomp doc Modified: trunk/docs/user-manual/en/interoperability.xml =================================================================== --- trunk/docs/user-manual/en/interoperability.xml 2010-04-26 13:18:12 UTC (rev 9164) +++ trunk/docs/user-manual/en/interoperability.xml 2010-04-26 13:27:05 UTC (rev 9165) @@ -45,23 +45,7 @@ (it will be ignored if its <literal>transaction</literal> header is set).</para> </section> </section> - <section id="stompconnect"> - <title>StompConnect</title> - <para><ulink url="http://stomp.codehaus.org/StompConnect">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.</para> - <para>To run StompConnect first start the HornetQ server and make sure that it is using - JNDI.</para> - <para>Stomp requires the file <literal>jndi.properties</literal> to be available on the - classpath. This should look something like:</para> - <programlisting>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</programlisting> - <para>Make sure this file is in the classpath along with the StompConnect jar and the - HornetQ jars and simply run <literal>java org.codehaus.stomp.jms.Main</literal>.</para> - </section> + <section> <title>Mapping Stomp destinations to HornetQ addresses and queues</title> <para>Stomp clients deals with <emphasis>destinations</emphasis> when sending messages and subscribing. @@ -124,6 +108,25 @@ </programlisting> </section> </section> + + <section id="stompconnect"> + <title>StompConnect</title> + <para><ulink url="http://stomp.codehaus.org/StompConnect">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.</para> + <para>To run StompConnect first start the HornetQ server and make sure that it is using + JNDI.</para> + <para>Stomp requires the file <literal>jndi.properties</literal> to be available on the + classpath. This should look something like:</para> + <programlisting>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</programlisting> + <para>Make sure this file is in the classpath along with the StompConnect jar and the + HornetQ jars and simply run <literal>java org.codehaus.stomp.jms.Main</literal>.</para> + </section> + </section> <section> <title>REST</title>