User: fleury
Date: 00/07/27 15:39:19
Modified: src/main/org/jboss/ejb/plugins/jrmp/server
JRMPContainerInvoker.java
Log:
It seems that the JRMPcontainerInvoker, relies on the thread implicitely passed
transaction. This is not correct. The thread should be clean and the tx passed with
the Method Invocation. That code is implemented elsewhere, here we just leave the
comments
Revision Changes Path
1.9 +4 -1
jboss/src/main/org/jboss/ejb/plugins/jrmp/server/JRMPContainerInvoker.java
Index: JRMPContainerInvoker.java
===================================================================
RCS file:
/products/cvs/ejboss/jboss/src/main/org/jboss/ejb/plugins/jrmp/server/JRMPContainerInvoker.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- JRMPContainerInvoker.java 2000/06/21 11:51:34 1.8
+++ JRMPContainerInvoker.java 2000/07/27 22:39:19 1.9
@@ -62,7 +62,7 @@
*
* @see <related>
* @author Rickard �berg ([EMAIL PROTECTED])
- * @version $Revision: 1.8 $
+ * @version $Revision: 1.9 $
*/
public abstract class JRMPContainerInvoker
extends RemoteServer
@@ -123,6 +123,8 @@
rmi.setMethodMap(homeMethodInvokerMap);
Transaction tx = rmi.getTransaction();
+//DEBUG System.out.println("The home transaction is "+tx);
+
System.out.println(container.getTransactionManager());
if (tx == null)
tx =
container.getTransactionManager().getTransaction();
@@ -150,6 +152,7 @@
rmi.setMethodMap(beanMethodInvokerMap);
Transaction tx = rmi.getTransaction();
+ // MF FIXME: there should be no implicit thread passing of the
transaction
if (tx == null)
tx = container.getTransactionManager().getTransaction();
