JTA Compliant

• Key: TRANSACTION-13
• Type: New Feature
• Status: Reopened
• Priority: Major
• Assignee: Unassigned
• Reporter: Cyrille
• Fix Version/s: 2.1

Description

Is there a plan to make Commons-Transaction compliant with JTA (Java Transaction API) ?
It would be great to get it.

For exemple, in case of a web file upload, we could make one transaction for tose 2 operations :
1) writing metadata in database (title,description...),
2) writing the file on the filesystem.

Comments

There are no such plans, but commons tx could serve as a basis for such an implementation

[Cyrille]

I think it is a must have feature, because nowdays Transactions are easilly integrated in a application (Spring, AppServer).
Do you know about that work ? Is it a difficult task ? I'm beginner with Java, so I'm afraid to tackle that subject.

Do you know some project about File Transaction and JTA ?

[Cyrille]

there is a discussion about that subject at forum.springframework.org

http://forum.springframework.org/showthread.php?t=32704

Thanks to Jörg !
Happy new year !

[Oliver Zeigermann]

With the new 2.0 version a JTA impelmentation should be a pretty easy thing to do. Except for one thing: an XA reaource (required for that implementation) needs to be able to start its work with one thread and continue with another one. However, this is incompatible with the new implementation of the lock manager. This new implementation is based on Java 1.5 locks which do not support transfer of ownership to other thread.

The lock manager is fully configurable, so maybe a different implementation would do. Options you be to extend Java 1.5 locks or to fall back the 1.x read/write-lock implementation.

[Oliver Zeigermann]

I'd be all for deferring this issue to 2.1 as I will require quite some effort. Concerning lock implementation: There now is a custom juc compatible Lock implementation which - at least principally - would allow passing over locks from one thread to another.

However, this will need more work to find an appropriate interface and protocol for something like that.

[Oliver Zeigermann]

Unless the ResourceRWLock gives us more freedom about the thread an action is exectured with we can not solve this issue.

[Geoffrey Wiseman]

Commons Transaction seems much more useful if I can synchronize it with a database transaction, I have to admit.

[Jorg Heymans]

It is not possible to vote on resolved issues, please leave the ticket open so people can vote on it.

[Richard Shu]

The JTA Compliant feature seems a very useful one; with that it'd be much easier to work with transaction managers like JOTM. Just wonder when this feature will be included in release.

[Henri Yandell]

Reopening as 'Later' is not a good part of JIRA workflow. Setting the fix version to 2.1 - ie "Later".