Author: jmesnil Date: 2010-02-08 04:58:51 -0500 (Mon, 08 Feb 2010) New Revision: 8866 Modified: trunk/docs/user-manual/en/messaging-concepts.xml trunk/examples/jms/bridge/readme.html Log: typos Modified: trunk/docs/user-manual/en/messaging-concepts.xml =================================================================== --- trunk/docs/user-manual/en/messaging-concepts.xml 2010-02-06 01:13:06 UTC (rev 8865) +++ trunk/docs/user-manual/en/messaging-concepts.xml 2010-02-08 09:58:51 UTC (rev 8866) @@ -202,14 +202,11 @@ <section> <title>STOMP</title> <para><ulink - url="http://en.wikipedia.org/wiki/Streaming_Text_Orientated_Messagin... - >Stomp</ulink> is a very simple protocol for interoperating with messaging + url="http://stomp.codehaus.org/" + >Stomp</ulink> is a very simple text protocol for interoperating with messaging systems. It defines a wire format, so theoretically any Stomp client can work with any messaging system that supports Stomp. Stomp clients are available in many different programming languages.</para> - <para>HornetQ can be used by any Stomp client when using the <ulink - url="http://stomp.codehaus.org/StompConnect">StompConnect<... broker which - translates the STOMP protocol to the JMS API.</para> <para>Please see <xref linkend="stomp"/> for using STOMP with HornetQ.</para> </section> <section> Modified: trunk/examples/jms/bridge/readme.html =================================================================== --- trunk/examples/jms/bridge/readme.html 2010-02-06 01:13:06 UTC (rev 8865) +++ trunk/examples/jms/bridge/readme.html 2010-02-08 09:58:51 UTC (rev 8866) @@ -16,10 +16,10 @@ choice for forwarding over unreliable connections, e.g. a WAN.</p> <p>They can also be configured with an optional filter expression, and will only forward messages that match that filter.</p> - <p>Furthermore they can be configured to use an optional Transformer class. A user defined Transformer class + <p>Furthermore they can be configured to use an optional Transformer class. A user-defined Transformer class can be specified which is called at forwarding time. This gives the user the opportunity to transform - the message in some way, e.g. changing it's properties or body</p> - <p>HornetQ also includes a <b>JMS Bridge</b>. This is similar in some ways to a core bridge, but uses the JMS API + the message in some ways, e.g. changing its properties or body</p> + <p>HornetQ also includes a <b>JMS Bridge</b>. This is similar to a core bridge, but uses the JMS API and can be used to bridge between any two JMS 1.1 compliant messaging systems. The core bridge is limited to bridging between HornetQ instances, but may provide better performance than the JMS bridge. The JMS bridge is covered in a separate example.</p>