Menu
▾
▴
#1136 throwsRemoteException in AbstractVerifier
closed-invalid
5
2004-08-31
2003-02-14
No
According to the RMI Spec. a remote interface must
throw a RemoteException so, I need to make sure that
the exception thrown is either a RemoteException or a
class that can be assigned to RemoteException (a
derived class).
Using
if( exception[i].isAssignableFrom
(java.rmi.RemoteException.class) )
this is not fully correct..
I suggest to replace with :
if (java.rmi.RemoteException.class.isAssignableFrom
(exception[i]))
This problem occurs with 3.0.6
Thank You
Roberto
Logged In: YES
user_id=176671
... i vaguely remember there being a reason why the test is
carried around this way (IIRC it was initially done the
other way around and changed because of some other bug).
i'll take a look at this.
Logged In: YES
user_id=9459
According to the RMI spec (2.4.1):
"A remote method declaration must include the exception
java.rmi.RemoteException (or one of its superclasses such as
java.io.IOException or java.lang.Exception) in its throws
clause,"