Perhaps an exceptions-dl.jar, which would only be required if an
exception was propagated from a jini 2.2.0 CDC node to a jini 2.1.2 or
earlier java SE node?
Seems the least complicated solution?
Peter Firmstone wrote:
Got a tricky question about java.rmi.UnmarshalException and
compatibility communicating with earlier versions of Jini.
For Java CDC, I'm missing java.rmi.UnmarshalException
UnmarshalException extends java.rmi.RemoteException, which I do have.
UnmarshalException has no Serialized state, nor does it have any
methods, only constructors.
I can't go changing all existing public API methods that throw it, to
throw say, net.jini.io.UnmarshalException since earlier platform
versions won't have the required class file.
I could throw RemoteException instead, however that might cause the
Exception to be caught higher up the call stack.
One solution seems to be to convert the serialized form to
java.rmi.RemoteException, and then change it back somewhere, perhaps
in JERI for java cdc?
Any ideas?
Cheers,
Peter.
