Two different subjects were mentioned here: (1) the best way of integrating the remoting-based DTM, which currently works only with the old TM, with JBossTS, and (2) the removal of the TM/DTM code from the current source branch. I suggested Jonathan to take the technical discussion of subject (1) to this forum, but am not sure this is the right place for discussing subject (2)... Anyway, given the decision of dropping the remoting-based DTM from JBAS 5.0, subject (2) appears to be the most urgent one. Mark mentioned that community work on the JBoss TM can continue. Will JBoss still support such work by keeping the TM in a JBoss-hosted source repository (even if not in the JBAS 5.0 branch) and by letting the TM sources be updated by the community? I ask the question above because a research project of mine relies on the TM code and is likely to produce updates on that code. (One of my M.Sc. students is finishing the implementation of a "WS-AT shell" over the TM code, which now fully supports logging and crash recovery.) This is academic work that may not fit into a professional open-source vision, so I am certainly not demanding JBoss/RH support to such a project. Should I fork the TM and take this project elsewhere? Or perhaps jboss.org would have interest in hosting it as a "community labs project"? Regards, Francisco View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976765#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...