[jboss-dev-forums] [Design of JBoss Transaction Services] - Re: ClientUserTransaction and TxPropogation inefficiencies

[mark.little@jboss.com]

"jhalliday" wrote : 
  | Then there is the question of what the behaviour should be when the client is using RMI/IIOP rather than JRMP for transactional calls to the server. Should it need the JBossTS libraries, or should it continue to use UT?  What if it wants to switch to JBossTS? Using either the JTA API or the CORBA API for transaction demarcation.

We shouldn't need any current JBossTS code at the client side if the client code indirects through JTS. The client should simply interact with the Current pseudo-object, which we know can be wrapped by a UserTransaction. The current UserTransactions in JBossTS would pull in too much of the JBossTS code. What we had in HP (written by Malik) was a small UT implementation that called directly to Current (or maybe it was TransactionFactory, I can't remember, but in which case it would also be doing thread-to-transaction association). I'll dig around and see if I can still find that code, because it's definitely not in the JBossTS sources at the moment.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173381#4173381

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173381