activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r797018 - /activemq/stomp/trunk/webgen/src/stomp10/
Date Thu, 23 Jul 2009 11:22:05 GMT
Author: dejanb
Date: Thu Jul 23 11:22:04 2009
New Revision: 797018

adding stomp jms bindings


Modified: activemq/stomp/trunk/webgen/src/stomp10/
--- activemq/stomp/trunk/webgen/src/stomp10/ (original)
+++ activemq/stomp/trunk/webgen/src/stomp10/ Thu Jul 23 11:22:04 2009
@@ -68,4 +68,45 @@
-	message-id: ID:12345
\ No newline at end of file
+	message-id: ID:12345
+#Stomp JMS Bindings
+When using the Stomp Protocol with [StompConnect](
or a JMS provider there are some additional Stomp headers and semantics which are useful to
know. In terms of JMS semantics Stomp supports the same ack modes unless the messages are
exchanged within a transaction via BEGIN/COMMIT/ABORT
+###Standard JMS Message Headers
+The following standard JMS Headers are mapped to Stomp as follows; so these headers can be
added to a SEND command when sending messages
+<tr><th>Stomp header</th><th>JMS header</th><th>Description</th></tr>
consumes will add this header to any responses they send so that entire conversations can
be correlated</td></tr>
+<tr><td>expires</td><td>JMSExpiration</td><td>the expiration
time of the message</td></tr>
or not the message is persistent</td></tr>
+<tr><td>priority</td><td>JMSPriority</td><td>the priority
on the message</td></tr>
+<tr><td>reply-to</td><td>JMSReplyTo</td><td>the destination
you should send replies to</td></tr>
+<tr><td>type</td><td>JMSType</td><td>sets the type of
the message</td></tr>
+###Subscription headers
+You can use an SQL 92 selector whenever you subscribe using the *selector* header
+	selector:location = 'London' and sex = 'M'
+When subscribing for a topic you can specify the header
+	no-local:true
+This will disable local messages. Namely messages published over the Stomp connection will
not be received by this topic subscription.
+###Durable Topic Subscribers
+If you wish to create a _durable topic subscriber_ you will need to do the following
++ set the _client-id_ header on the CONNECT to a globally unique String for the Stomp connection
++ set the _durable-subscriber-name_ header on the SUBSCRIBE command.
+The combination of the *client-id* and *durable-subscriber-name* uniquely identifies the
durable topic subscription. i.e. after you restart your program and re-subscribe, the Broker
will know which messages you need that were published while you were away 

View raw message