"david.lloyd(a)jboss.com" wrote : | Remoting has no state, or direct awareness of transactions. However, whatever service you're connecting to by way of Remoting may (and probably does). The reason Remoting 3 has this capability is so that there's a single standard way to propagate transaction state between endpoints - whether it's a database to an app server, two app servers together, or two client applications that don't even know anything about JTA or JCA or anything like that. | I don't understand. Unless I've misunderstand your requirement. What you describe is called OTS/JTS. It's already a standard and is probably a lot more complicated than you've envisoned to do correctly and efficiently. :-) There's also already an implementation of JTS that uses remoting in JBoss5 - see the transaction project, but we are dropping it in favour of JBoss JTS (which should be augmented with a version that runs over remoting rather than just RMI/IIOP). There's also some overlap with transactional webservices. You need to speak to the transaction team and make sure you are on the same page. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086052#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...