Furthermore, it is completely idiotic and gay to develop a new and different interface other than JTA if I want to use two non-XA enabled resources in the same unit of work. JTA is a great abstraction and has very tight integration with things like EJB to make your life tons easier. BTW, you're the same guy who tried to argue with me that JTA is useless when you have only one resource in your transaction. Anyways, there is absolutely nothing wrong with using multiple non-XA resources in same TX if a) you can't make them all XA and/or b) more importantly, you are aware of the consequences. Forcing users ,for the sake of purity, to refactor their applications when they are aware the problem exists is just plain pompus. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989313#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...