[
https://issues.apache.org/jira/browse/TRANSACTION-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516171
]
Oliver Zeigermann commented on TRANSACTION-13:
----------------------------------------------
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.
> JTA Compliant
> -------------
>
> Key: TRANSACTION-13
> URL: https://issues.apache.org/jira/browse/TRANSACTION-13
> Project: Commons Transaction
> Issue Type: New Feature
> Reporter: Cyrille
> Assignee: Jörg Heinicke
> Fix For: 2.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
