From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Cc: | Michael Allman <msa(at)allman(dot)ms> |
Subject: | XADataSource implementation |
Date: | 2005-08-28 07:34:17 |
Message-ID: | Pine.OSF.4.61.0508281032490.283830@kosh.hut.fi |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi,
I've been working on the XADataSource implementation. Patch attached. Test case
is in the separate zip file, because I couldn't get cvs to include it in the
diff.
I looked at Micheal Allman's implementation, but decided to continue working on
my original version instead. Michael's implementation was perhaps more
ambitious, it had more thorough bookkeeping for resource associations and xids.
Unfortunately there's no straightforward way to implement the full XA interface
in a spec-compliant way. I did copy some snippets and test cases from Michael's
code that were useful, though.
Thanks Michael for your hard work, it was a lot of help anyway!
This implementation doesn't try to support transaction interleaving as required
by the XA spec. Instead, it throws an exception saying it's not supported.
I tested it with the JOnAS application server (after fixing some recovery bugs
in JOnAS itself :), and it seems to be fine with the limitations. It needs
testing with other application servers to see if the limitations matter for
them.
Anyone with access to WebLogic, WebSphere etc: please help! I can send the
simple servlet I used to test JOnAS if you're interested.
BTW: How does the translation work? What strings need to be translated?
- Heikki
Attachment | Content-Type | Size |
---|---|---|
testcase.zip | application/zip | 2.3 KB |
xadatasource-heikki-20050827.diff.zip | application/zip | 15.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2005-08-28 10:39:23 | Re: XADataSource implementation |
Previous Message | Kris Jurka | 2005-08-26 19:41:49 | Re: implementing asynchronous notifications PLEASE CONFIRM |