On Friday 15 January 2010 11:44 PM, glassfish_at_javadesktop.org wrote:
> Hello Nigel,
> thank you for that clarification!
> Do you have a reference in a spec for that?
> I found two sites:
> http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs90/jms/trans.html#1028577
> and
> http://www.theserverside.com/news/thread.tss?thread_id=23151#105935
> but I couldn't find that in the JEE5 spec. I need something to convince my co workers ;).
Section 8.5 of the JMS 1_1 Specification:
> It is important to note that a distributed transaction context does not flow with
> a message; that is, the receipt of the message cannot be part of the same
> transaction that produced the message. This is the fundamental difference
> between messaging and synchronized processing. Message producers and
> consumers use an alternative approach to reliability that is built upon a JMS
> provider ’s ability to supply a once-and-only-once message delivery guarantee.
> To reiterate, the act of producing and/or consuming messages in a Session can
> be transactional. The act of producing and consuming a specific message across
> different sessions cannot.
Does this work :) ?
Thanks
--Siva.
> Best regards,
> Matthias
> [Message sent by forum member 'matthiasfraass' (matthias.fraass_at_tricoder.net)]