rmi.Naming and registry

From: staff (pawelstawicki_at_gazeta.pl.nospam)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 16:04:21 +0200

Hello,

I am having a following problem. When I create rmi registry in my
application by

LocateRegistry.createRegistry(Registry.REGISTRY_PORT);

and I register objects in it everything is ok. I am registering by

Naming.rebind("RemoteName", remoteInterfaceImplInstance);

Problems are coming up when registry is already created by other
application. Then Naming.rebind(...) throws exception ClassNotFound ....
RemoteInterfaceImpl_Stub.

Looks like registry has no access to this class, how to make such access for
already created registry?

Regards
Paweł Stawicki

Relevant Pages

  • Re: JAVA RMI register problem
    ... registry running at diffrent port ... you have more than one RMI registry. ... Every RMI server needs to be bound to a ... RMI registry, but that registry does not need a different port for each RMI ...
    (comp.lang.java.programmer)
  • Destroy RMI Registry programmatically
    ... i got a little question about the Java RMI Registry. ... In our Software use a RMI Registry. ... Instead of doing this by starting an rmid we start the registry directly in the Code. ...
    (comp.lang.java.programmer)
  • Re: rmi, two binding methods, what differences?
    ... Registry registry = LocateRegistry.getRegistry; ... It seems A has to use a port, which may need a special setting over ... firewall; for B, what's the port number? ... It shouldn't be because it is reserved by IANA for the RMI Registry. ...
    (comp.lang.java.programmer)
  • Re: Routing problem with RMI Registry
    ... start RMI registry from within my program (and shut it down after I'm ... command-line RMI registry doesn't support SSL, ...
    (comp.lang.java.programmer)
  • Re: rmi, two binding methods, what differences?
    ... Registry registry = LocateRegistry.getRegistry; ... It seems A has to use a port, which may need a special setting over ... firewall; for B, what's the port number? ... So if it's in use it *should* mean that the RMI Registry is already running. ...
    (comp.lang.java.programmer)