I spent some time today with this issue. I just want to throw some ideas
to fix this.
First option:
If you have 4.0:MarshalledInvocation.useFullHashMode=false, and
3.2:MarshalledInvocation.useFullHashMode=false, the testsuite should
pass.
So, we could change FullHashMode to false if some parameter is avaible,
and 3.2.8.sp1 would be compatible with 4.0.4, but not 3.2.8. The easiest
way would be have a parameter to change the FullHashMode on 4.0
Second option:
We could also have an interface on RMIAdaptorImpl and change
MarshalledInvocation to do something like:
public static Map getInterfaceHashes(Class intf)
{
If (intf <implements> ThatInterface)
{
ThatINterface that = (ThatInterface)intf.newInstance();
... delegate the hashCalculation to that, somehow.
}
}
I don't like this idea, but I just wanted to throw something on the
discussion, as a brain storm.
Third options:
An option also, would be to back port RMIAdaptor from 4.0.x to 3.2.8,
but that would break compatibility between 3.2.8 and previous versions,
and I don't know if there is a way to have a selective classLoading
between a newer and an older version.
Any other idea/option?
Thoughts?
Clebert Suconic
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
