Re: [JBoss-dev] Distributed Transaction Manager support (coming up)
Anatoly Akkerman wrote: Hi, For the past couple of weeks I've been integrating Tyrex DTM (tyrex.exolab.org) into JBoss. Things are coming along and in a few days I'll probably have a basic support for transaction propagation across 2 JBoss instances. I was wondering, how should I make my mods available (the code is really alpha) for the people who want to start working on it. The code also requires changes to the current JBoss implementation (in particular, TxInterceptorCMT and TxInterceptorBMT would rely on javax.transactions.TransactionManager interface to manage transactions, instead of using JBoss extensions to the API for thread association/disassociation. If it breaks things, you might want to create a CVS branch. Something like: cvs rtag Tyrex_BP jboss cvs rtag -b Tyrex_Branch jboss Then: cvs co -rTyrex_Branch jboss Then, put your changes in and commit. Later, when it's all working, you can do: cvs co jboss cd jboss cvs update -jTyrex_Branch and you should get an automated merge (which you'll need to fix manually). Unless I've screwed the whole concept up completely. Perhaps a resident CVS guru would care to comment? Toby. ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
RE: [JBoss-dev] Distributed Transaction Manager support (coming up)
Hey, Anatoly Akkerman wrote: Hi, For the past couple of weeks I've been integrating Tyrex DTM (tyrex.exolab.org) into JBoss. Things are coming along and in a few days I'll probably have a basic support for transaction propagation across 2 JBoss instances. I was wondering, how should I make my mods available (the code is really alpha) for the people who want to start working on it. The code also requires changes to the current JBoss implementation (in particular, TxInterceptorCMT and TxInterceptorBMT would rely on javax.transactions.TransactionManager interface to manage transactions, instead of using JBoss extensions to the API for thread association/disassociation. Try to drop an email to Ole Husgaard, I know that he also has a DTM working and well tested, just to avoid that tomorrow also him will commit his changes ending up to have 2 DTM, maybe incompatible WRT the changes to TxInterceptors. If it breaks things, you might want to create a CVS branch. Definitely do create the branch. Something like: cvs rtag Tyrex_BP jboss cvs rtag -b Tyrex_Branch jboss Then: cvs co -rTyrex_Branch jboss Then, put your changes in and commit. Later, when it's all working, you can do: cvs co jboss cd jboss cvs update -jTyrex_Branch and you should get an automated merge (which you'll need to fix manually). Unless I've screwed the whole concept up completely. Perhaps a resident CVS guru would care to comment? Toby, no comments, it's everything OK :) Anatoly, just be sure to know how CVS merge works before updating with -j option. Drop me an email if you're not sure. Simon ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Distributed Transaction Manager support (coming up)
Hi, For the past couple of weeks I've been integrating Tyrex DTM (tyrex.exolab.org) into JBoss. Things are coming along and in a few days I'll probably have a basic support for transaction propagation across 2 JBoss instances. I was wondering, how should I make my mods available (the code is really alpha) for the people who want to start working on it. The code also requires changes to the current JBoss implementation (in particular, TxInterceptorCMT and TxInterceptorBMT would rely on javax.transactions.TransactionManager interface to manage transactions, instead of using JBoss extensions to the API for thread association/disassociation. - Anatoly Akkerman Computer Science Dept. Courant Institute of Mathematical Sciences, NYU 719 Broadway, #715 Tel: 212 998-3525 New York, NY 10003 Fax: 212 995-4123 - ___ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
