[
https://issues.apache.org/jira/browse/TRANSACTION-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503689
]
Jörg Heinicke commented on TRANSACTION-16:
------------------------------------------
It was more a rhetorical question to answer it directly with your mail. The
point of the patch/this issue was just missing.
Since I can edit the description of this issue I have moved the quote of your
mail into it.
Did you have a look at the XA stuff in ctx that's already there? I know it's
not much, just the maps ...
I also worked on TRANSACTION-13, but didn't find the time to complete it
recently. I might add the stuff I already have to that issue. It misses the
connection management. Maybe you can have a look at it.
What I found strange from a short look on your code was the access to the
TransactionManager. IMO this should not happen. It's up to the
TransactionManager to enlist a resource, not the other way around.
But thanks for your contribution anyway. I'm looking forward to your future
involvement.
> TX collections / TX object model
> --------------------------------
>
> Key: TRANSACTION-16
> URL: https://issues.apache.org/jira/browse/TRANSACTION-16
> Project: Commons Transaction
> Issue Type: Wish
> Reporter: Dennis Thrysøe
> Assignee: Oliver Zeigermann
> Attachments: buzz.zip
>
>
> (Quoted from the original message:
> http://marc.info/?l=jakarta-commons-dev&m=118129603213307&w=4):
> I would like to donate an implementation of some transaction enabled
> collections and resources.
> The implementation is (more or less) JTA compliant, and mostly finished. It
> is not well-tested, robust or mature.
> The code includes:
> 1) TX collections: Map, Set and List wrappers for transactional
> protection/isolation. Supported nested collections such that for instance a
> List or Set in a transactional Map is wrapped in the appropriate wrapper.
> Copy-on-tx-start and locking.
> 2) TX object model: An object is passed to the wrapper and after that only
> used when retrieved from the wrapper. The object is wrapped in a dynamic
> proxy which makes sure all returned objects from reachable instances are also
> wrapped. Copy-on-write and locking. I have some additional ideas on this one.
> ---------------------------------------------
> I hereby donate the attached source code for inclusion in or inspiration for
> commons-transaction.
> I will be happy to participate further in the development of these features.
> Some of the stuff in the project can be considered experimental, and not yet
> done, but most is fully implemented.
> -dennis
--
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]
