> Another problem I see is that the TxMethod map is required on the client > side as well. Makes proxies even more heavy and what do you do about a hot > deploy?
The hot deploy is a general issue with proxies. Whether or not this works depends on the transport endpoint. RMI/JRMP proxies do not work across a hot deploy, and most p2p transports do not. Making the proxies more robust across hot deploys using our own transports, etc. is something we should work towards. A java.lang.reflect.Method map is a very anti-hot-deploy construct because of the strong typing of the Method to its class. We should certainly look to limit the exposure of such a mapping outside of the VM. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Bill Burke" <[EMAIL PROTECTED]> To: "David Jencks" <[EMAIL PROTECTED]>; "Jboss-Dev" <[EMAIL PROTECTED]> Sent: Wednesday, February 12, 2003 1:31 PM Subject: [JBoss-dev] TxInterceptor split is bad > What if you don't have java on the client side? What if you're CORBA with > OTS? You're making it harder for Non-JBoss/Java clients to integrated with > us. I think this split should be undone. > > BTW, why the split besides code readability? Is the DTM dependent on this > at all? Is the TM even accessed on the client side? > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
