java.lang.Object
   org.springframework.remoting.support.RemotingSupport
      org.springframework.remoting.support.RemoteAccessor
         org.springframework.remoting.support.UrlBasedRemoteAccessor
            org.springframework.remoting.support.RemoteInvocationBasedAccessor
               org.springframework.remoting.rmi.RmiClientInterceptor
                  org.springframework.remoting.rmi.RmiProxyFactoryBean

All Implemented Interfaces:
    BeanClassLoaderAware, FactoryBean, org.aopalliance.intercept.MethodInterceptor, InitializingBean

The service URL must be a valid RMI URL like "rmi://localhost:1099/myservice". RMI invokers work at the RmiInvocationHandler level, using the same invoker stub for any service. Service interfaces do not have to extend java.rmi.Remote or throw java.rmi.RemoteException. Of course, in and out parameters have to be serializable.

With conventional RMI services, this proxy factory is typically used with the RMI service interface. Alternatively, this factory can also proxy a remote RMI service with a matching non-RMI business interface, i.e. an interface that mirrors the RMI service methods but does not declare RemoteExceptions. In the latter case, RemoteExceptions thrown by the RMI stub will automatically get converted to Spring's unchecked RemoteAccessException.

The major advantage of RMI, compared to Hessian and Burlap, is serialization. Effectively, any serializable Java object can be transported without hassle. Hessian and Burlap have their own (de-)serialization mechanisms, but are HTTP-based and thus much easier to setup than RMI. Alternatively, consider Spring's HTTP invoker to combine Java serialization with HTTP-based transport.

Also see:

setServiceInterface
setServiceUrl
RmiClientInterceptor
RmiServiceExporter
java.rmi.Remote
java.rmi.RemoteException
org.springframework.remoting.RemoteAccessException
org.springframework.remoting.caucho.HessianProxyFactoryBean
org.springframework.remoting.caucho.BurlapProxyFactoryBean
org.springframework.remoting.httpinvoker.HttpInvokerProxyFactoryBean
author: Juergen - Hoeller

since: 13.05.2003 -

 public  void afterPropertiesSet() 
{
		super.afterPropertiesSet();
		if (getServiceInterface() == null) {
			throw new IllegalArgumentException("Property 'serviceInterface' is required");
		}
		this.serviceProxy = new ProxyFactory(getServiceInterface(), this).getProxy(getBeanClassLoader());
}

 public Object getObject() 
{
		return this.serviceProxy;
}

 public Class getObjectType() 
{
		return getServiceInterface();
}

 public boolean isSingleton() 
{
		return true;
}