[ http://issues.apache.org/jira/browse/GERONIMO-2277?page=all ]
Dain Sundstrom updated GERONIMO-2277:
-------------------------------------
Attachment: GERONIMO-2277.patch
I merged all changes from head back into notcm and fixed the m2 build. I also
made a few changes noted below based on requests for David. I suggest you test
the notcm branch directly. If you want to try the merge, use the same command
as before, and you'll have to resolve some conflicts (I have no idea why svn
marks them as conflicts). Here are the commands I used:
svn co https://svn.apache.org/repos/asf/geronimo/trunk geronimo
cd geronimo
svn merge -r 427246:HEAD
https://svn.apache.org/repos/asf/geronimo/branches/dain/notcm .
# resolve the conflicts by taking the files from notcm
mv bootstrap.merge-right* \
bootstrap
svn resolved bootstrap
chmod u+x bootstrap
mv pom.xml.merge-right* \
pom.xml
svn resolved pom.xml
mv
m2-assemblies/geronimo-boilerplate-j2ee/src/main/resources/var/security/keystores/geronimo-default.merge-right*
\
m2-assemblies/geronimo-boilerplate-j2ee/src/main/resources/var/security/keystores/geronimo-default
svn resolved
m2-assemblies/geronimo-boilerplate-j2ee/src/main/resources/var/security/keystores/geronimo-default
mv
m2-assemblies/geronimo-boilerplate-minimal/src/main/resources/var/security/keystores/geronimo-default.merge-right*
\
m2-assemblies/geronimo-boilerplate-minimal/src/main/resources/var/security/keystores/geronimo-default
svn resolved
m2-assemblies/geronimo-boilerplate-minimal/src/main/resources/var/security/keystores/geronimo-default
# run the m2 build or run the m1 build
./bootstrap
mvn clean install
# maven new
> 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
>
> Attachments: GERONIMO-2277.patch
>
>
> 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
