|
Spring Framework example source code file (RmiProxyFactoryBean.java)
The Spring Framework RmiProxyFactoryBean.java source code/* * Copyright 2002-2008 the original author or authors. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an "AS IS" BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ package org.springframework.remoting.rmi; import org.springframework.aop.framework.ProxyFactory; import org.springframework.beans.factory.BeanClassLoaderAware; import org.springframework.beans.factory.FactoryBean; /** * FactoryBean for RMI proxies, supporting both conventional RMI services and * RMI invokers. Exposes the proxied service for use as a bean reference, * using the specified service interface. Proxies will throw Spring's unchecked * RemoteAccessException on remote invocation failure instead of RMI's RemoteException. * * <p>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 <code>java.rmi.Remote * or throw <code>java.rmi.RemoteException. Of course, in and out parameters * have to be serializable. * * <p>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. * * <p>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. * * @author Juergen Hoeller * @since 13.05.2003 * @see #setServiceInterface * @see #setServiceUrl * @see RmiClientInterceptor * @see RmiServiceExporter * @see java.rmi.Remote * @see java.rmi.RemoteException * @see org.springframework.remoting.RemoteAccessException * @see org.springframework.remoting.caucho.HessianProxyFactoryBean * @see org.springframework.remoting.caucho.BurlapProxyFactoryBean * @see org.springframework.remoting.httpinvoker.HttpInvokerProxyFactoryBean */ public class RmiProxyFactoryBean extends RmiClientInterceptor implements FactoryBean, BeanClassLoaderAware { private Object serviceProxy; 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; } } Other Spring Framework examples (source code examples)Here is a short list of links related to this Spring Framework RmiProxyFactoryBean.java source code file: |
... this post is sponsored by my books ... | |
#1 New Release! |
FP Best Seller |
Copyright 1998-2024 Alvin Alexander, alvinalexander.com
All Rights Reserved.
A percentage of advertising revenue from
pages under the /java/jwarehouse
URI on this website is
paid back to open source projects.