Re: [dna-dev] Non-XA compliant resource participation in distributed transactions
If you're using JBossTS (which I think you guys are now) then you have
that capability from the transaction engine. Go in via JTA and if you
have a 1PC-aware resource then just ensuring it is enlisted as such:
JBossTS will take care of everything else.
Mark.
On 14 May 2008, at 22:10, John P. A. Verhaeg wrote:
Seems like we ought to strive to support n-1 XA resources for
distributed transactions, allowing for the last participant in a
transaction (thus, this participants updates can't be done in
parallel with the other resources) to not support XA transactions,
but still participate in a distributed transaction with other XA-
compliant resources. Unlike compensating transactions, the non-XA
participant would appear transactional and none of the updates would
be visible until the entire transaction was complete. It seems like
this could open up many more possible configurations for customers.
_______________________________________________
dna-dev mailing list
dna-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/dna-dev
----
Mark Little
mlittle(a)redhat.com
JBoss, a Division of Red Hat
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No. 3798903
Directors: Michael Cunningham (USA), Charlie Peters (USA), Matt
Parsons (USA) and Brendan Lane (Ireland).