From: <ad...@jb...> - 2005-04-27 21:04:08
|
"reverbel" wrote : [ | No, the transaction manager must be aware of remote access, as it must know a set of interfaces implemented by remote access providers. It must keep references to remote resources (which implement a Resource interface), a reference to a parent coordinator (which implement a Coordinator interface), etc. It must call methods on remote Resource and Coordinator objects at appropriate times. | I'm saying these should be core the interfaces. Whether the implementations actually do remote work or are optimized for local tx management is a deployment decision. What I'm really after is the ability to plugin any TM and if it doesn't support certain features like Tx propogation over Remoting or the JCA XATerminator then there is a standard mechanism to integrate those features (or not if they are not required, e.g. mocks for testing purposes). This might be "pie in the sky" but it is an ideal we should aim for, even if it is not entirely attainable. That is how TransactionLocal works with a an implementation based on tx synchronization if the transaction manager does not directly support it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875662#3875662 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875662 |