| Service exporter which binds RMI services to JNDI.
Typically used for RMI-IIOP (CORBA).
Exports services via the
javax.rmi.PortableRemoteObject class.
You need to run "rmic" with the "-iiop" option to generate corresponding
stubs and skeletons for each exported service.
Also supports exposing any non-RMI service via RMI invokers, to be accessed
via
JndiRmiClientInterceptor /
JndiRmiProxyFactoryBean 's
automatic detection of such invokers.
With an RMI invoker, RMI communication works on the
RmiInvocationHandler level, needing only one stub for any service. Service interfaces do not have to
extend java.rmi.Remote or throw java.rmi.RemoteException
on all methods, but in and out parameters have to be serializable.
The JNDI environment can be specified as "jndiEnvironment" bean property,
or be configured in a jndi.properties file or as system properties.
For example:
<property name="jndiEnvironment">
<props>
<prop key="java.naming.factory.initial">com.sun.jndi.cosnaming.CNCtxFactory</prop>
<prop key="java.naming.provider.url">iiop://localhost:1050</prop>
</props>
</property>
author:
Juergen Hoeller
since:
1.1
See Also: JndiRmiServiceExporter.setService
See Also: JndiRmiServiceExporter.setJndiTemplate
See Also: JndiRmiServiceExporter.setJndiEnvironment
See Also: JndiRmiServiceExporter.setJndiName
See Also: JndiRmiClientInterceptor
See Also: JndiRmiProxyFactoryBean
See Also: javax.rmi.PortableRemoteObject.exportObject | 