skaffman
Jan 14th, 2006, 11:37 AM
I have a need to expose a service object over RMI without using a registry, be it rmiregistry or JNDI. The service's "stub" would be passed manually to the clients by other means.
If I were doing this by hand, without Spring, I'd use UnicastRemoteObject.exportObject() to produce a stub, wrap that stub in my business interface, and pass that around.
If I'm understanding the Spring API correctly, the only two classes which do something similar to this are RmiServicRxporter and JndiRmiServiceExporter. Unfortunately, both of there assume the presense of a registry to bind into, which I don't need or want. Their common superclass, RmiBasedExporter, does the useful work, but it has no other subclasses.
Am I missing something here, or over-complicating things?
If I were doing this by hand, without Spring, I'd use UnicastRemoteObject.exportObject() to produce a stub, wrap that stub in my business interface, and pass that around.
If I'm understanding the Spring API correctly, the only two classes which do something similar to this are RmiServicRxporter and JndiRmiServiceExporter. Unfortunately, both of there assume the presense of a registry to bind into, which I don't need or want. Their common superclass, RmiBasedExporter, does the useful work, but it has no other subclasses.
Am I missing something here, or over-complicating things?