> Actually it does support this, but in a limited way. Firebird has a
> API call to reconnected to a transaction from saved transaction id.
> The restrictions are signficant: The transaction must be in limbo,
> and once reconnected, the only options are to commit and to rollback.

Where do I find more info on the calls to reconnect transaction in limbo? Is
that only part of gfix (Services API)?

> I believe, however, that these are the necessary and sufficient
> conditions to implement a distributed transaction manager. The
> functionality has been in the product since the original alpha in
> 1985.

I need to check the specs to see if JTA expects transaction to be working
without any limitation after resume. Personally I cannot imagine any case
except JCA with connection pooling where reconnecting transaction in other
connection object would make sense.

Roman