HI Trenton,
This might not be the right place for it but ... RemoteException is
checked because you have to understand that it can happen (and
occasionally will) and you have to think about what can be done to
recover (even if you ultimately decide to just to "fail" by throwing
some other exception). The "distributed computing can be transparent"
myth was debunked years ago (I used to work with a system that tried it
and nicely demonstrated why it didn't work!).
Jim Waldo has a famous paper on this topic "Notes on Distributed Computing":
http://research.sun.com/techrep/1994/abstract-29.html
Cheers,
David Holmes
Senior Java Technologist
Java SE VM Real-time and Embedded Group
---------------------------------------
Trenton D. Adams said the following on 08/30/08 06:21:
Hi Guys,
Is this the right list to be discussing RMI topics? I saw some RMI related
stuff when I did a site search on google.
I'm curious what the reasoning is behind leaving RemoteException as a checked
exception. It seems to me that it would be more relevant to have it as a
RuntimeException, as there is not a whole lot one can do about it.
Any ideas why it might be that way? If there is agreement that it should be an
unchecked exception, any hope of moving toward it being unchecked?
Thanks.
Trenton D. Adams
Systems Analyst/Web Software Engineer
Navy Penguins at your service!
Athabasca University
(780) 675-6195
:wq!
__
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---
