Ok, that is good. Yes we need to limit the use of the most strongly typed components to where absolutely necessary to improve the robustness of the framework level components. A MethodHash should not change across hot deployments unless the method signature has changed and I believe this is the case today as we don't include any class identity info like hashCodes do we?
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "David Jencks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 12, 2003 7:16 PM Subject: Re: [JBoss-dev] TxInterceptor split is bad > In this case the client side method to tx support map uses MethodHash > values as keys since the Methods themselves are not serializable. Seems to > me that we should put the MethodHash values in the invocation to start > with. > > david ------------------------------------------------------- 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
