On 06/14/2010 01:15 PM, Patrick Wright wrote:
spec. I think it would be odd to try and change this convention now. OTOH, the specification specifically allows a superclass of RemoteException to be used http://java.sun.com/javase/6/docs/platform/rmi/spec/rmi-objmodel5.html
The superclass would not solve the problem of the broken java (clones) with the missing java.rmi.* package. Or was there another reason for doing this? It is a convention, but still one that is verified by the export AFAIR. And if one is thrown (RemoteException) and it is de-serialized we need to intercept the deserialization at the client side in order to change to class reference. So if we want deployment on non-java.rmi platforms. we need to do away with it at both the server and the client side.
Gr. Sim
