[ http://issues.apache.org/jira/browse/GERONIMO-2277?page=all ]
Dain Sundstrom updated GERONIMO-2277:
-------------------------------------
Patch Info: [Patch Available]
The best way to test this chang is to use svn merge directly instead of using
the patch commnd. This is because the svn merge handles adding, removing and
relocating files. To merge the changes from the notcm branch execute the
following command from within geronimo/trunk
svn merge -r 427246:HEAD
https://svn.apache.org/repos/asf/geronimo/branches/dain/notcm .
You should not receive any conflicts during the merge. Once this is complete,
run the following commands to remove the existing openejb checkout and checkout
the new related openejb code (this will be merged directly in openejb):
rm -rf openejb/
maven m:co
Then simply run the maven build with the following command:
maven install
Altermatively, you can use the attached patch insted of the svn merge command.
> Remove TransactionContextManager
> --------------------------------
>
> Key: GERONIMO-2277
> URL: http://issues.apache.org/jira/browse/GERONIMO-2277
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: transaction manager
> Reporter: Dain Sundstrom
> Assigned To: Dain Sundstrom
> Fix For: 1.2
>
>
> If you use the Geronimo TransactionContextManager, you can't use the
> TransactionManager interface directly since the TCM needs to know about all
> TM calls. Additionally, to use the TCM you must demarcate all changes in
> "component context" by starting an unspecified transaction context. This is
> all quite invasive and makes it hard to use our code in third part
> environments such as Spring or plain old Tomcat.
> I propose we remove the TransactionContextManager and replaced all uses with
> a plain old TransactionManager. This will also allow us to removed all code
> from web containers, app client and timer that was simply demarcating an
> unspecified transaction context, which is no longer needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
