public class RemoteAccessException extends NestedRuntimeException
When using conforming proxies, switching the actual remoting protocol e.g. from Hessian to Burlap does not affect client code. Clients work with a plain natural Java business interface that the service exposes. A client object simply receives an implementation for the interface that it needs via a bean reference, like it does for a local bean as well.
A client may catch RemoteAccessException if it wants to, but as remote access errors are typically unrecoverable, it will probably let such exceptions propagate to a higher level that handles them generically. In this case, the client code doesn't show any signs of being involved in remote access, as there aren't any remoting-specific dependencies.
Even when switching from a remote service proxy to a local implementation of the same interface, this amounts to just a matter of configuration. Obviously, the client code should be somewhat aware that it might be working against a remote service, for example in terms of repeated method calls that cause unnecessary roundtrips etc. However, it doesn't have to be aware whether it is actually working against a remote service or a local implementation, or with which remoting protocol it is working under the hood.
Modifier and Type | Field and Description |
---|---|
private static long |
serialVersionUID
Use serialVersionUID from Spring 1.2 for interoperability
|
Constructor and Description |
---|
RemoteAccessException(java.lang.String msg)
Constructor for RemoteAccessException.
|
RemoteAccessException(java.lang.String msg,
java.lang.Throwable cause)
Constructor for RemoteAccessException.
|
contains, getMessage, getMostSpecificCause, getRootCause
private static final long serialVersionUID
public RemoteAccessException(java.lang.String msg)
msg
- the detail messagepublic RemoteAccessException(java.lang.String msg, java.lang.Throwable cause)
msg
- the detail messagecause
- the root cause (usually from using an underlying
remoting API such as RMI)