STOMP interface does not support atomicity with transactions?

[any2xml]

Just tried running a putty session to STOMP interface (see below). Eventhough I aborted, the message was delivered? I followed the STOMP docs at http://stomp.codehaus.org/Protocol

CONNECT

^@

CONNECTED

         session:ID:nsdemo-2708-1255617439613-4:5

                                                 BEGIN

transaction: TRAN03

^@

SEND

destination: /queue/this.should.not.be.there

this message should not reach the destination

^@

ABORT

transaction: TRAN03

^@

[pedroneveu]

Hi any2xml,

As I understand it, once you are in the context of a transaction everything you do (like SEND, COMMIT, ABORT, and ACK) has to be in that context.

So, in your example you would have to send your message in the context of transaction TRAN03, like this:

^@

SEND

destination: /queue/this.should.not.be.there

transaction: TRAN03

this message should not reach the destination

^@

In that case if you abort you will have sent the message "this message should not reach the destination".

"SEND" outside of the context of TRAN03 is not committed to adhere to that transaction.

Have I understood your question or were you talking about something else?

Pedro