From: | Michael Allman <msa(at)allman(dot)ms> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: jdbc xa support |
Date: | 2005-07-22 02:06:45 |
Message-ID: | 20050721220519.U75792@yvyyl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, 22 Jul 2005, Oliver Jowett wrote:
> Michael Allman wrote:
>
>>> 4. recover is broken because it ignores the flags argument. That's
>>> going to cause an endless loop in the transaction manager when it
>>> tries to recover. See this discussion:
>>> http://forum.java.sun.com/thread.jspa?threadID=475468&messageID=2232566
>>
>>
>> That is problematic. The API for recovery is stateful, and, IMHO,
>> poorly designed. If you look at the original DTP XA spec you'll see it
>> makes much more sense.
>
> Huh? TMSTARTRSCAN etc are in the original DTP XA spec too, assuming you
> mean this one:
>
> X/Open CAE Specification
> Distributed Transaction Processing: The XA Specification
> ISBN: 1 872630 24 3
> X/Open Document Number: XO/CAE/91/300
Yes, and if you look at the specification for the xa_recover() function 47
you see it's a lot different from its Java counterpart.
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2005-07-22 02:26:10 | Re: Timestamp Conversion Woes Redux |
Previous Message | Oliver Jowett | 2005-07-22 02:02:24 | Re: jdbc xa support |