Hi,
I've been having some thoughts about what Chris said about using
IOException where possible for clients using non remote classes and
interfaces, instead of RemoteException.
We have plenty of methods that declare they throw RemoteException, we
could change them to declare throws IOException, without breaking binary
compatibility as it doesn't change the method signature. We can
continue throwing a RemoteException, but just change the declaration, so
clients using non remote interfaces and classes can catch an
IOException, without needing to create any dependency on
java.rmi.RemoteException.
Thoughts?
Peter.
- Replace RemoteException with IOException Peter Firmstone
-