Okay, I finally tracked down the cause of the problem I was having
late last week. You can't call toString on a client stub! I had a
println("result was: "+result) and it causes the problem where the stub
calls back to the server but the Method parameter comes through as null.
Perhaps because toString is not declared in the remote interface? I'm not
really sure.
So, can someone give me some pointers on where the client stub
"Proxy" objects are generated, so we can figure out why they're going back
to the server for toString, and why they're blowing up when they get
there?
Thanks,
Aaron
