Peter, >>I was also getting this sending one of my classes from the client to the >>server (most things go from server->client, this is the most complex thing >>going back to the server): >> > >success! learn something new every day. The altrmi behavior is different from >the standard RMI behavior, I'm not sure why. > >The class in question had an import statement to a class that was not in the >servers classpath, and thus the exceptions. I figured it out when I changed >the method definition on the server method that was being called to be the >concrete class that was being passed rather than the interface. > Yes, that is going to lead to loads of problems in the future. What is a facade and what is a value object requires intricate knowledge of the class model in question. I think a fail amount of support will be on that, unless AltRMI can be smart enough to issue appropriate messages.
Regards, - Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
