This week's book giveaways are in the Java EE and JavaScript forums.
We're giving away four copies each of The Java EE 7 Tutorial Volume 1 or Volume 2(winners choice) and jQuery UI in Action and have the authors on-line!
See this thread and this one for details.
The moose likes Distributed Java and the fly likes The difference of start rmiregistry by API and Command line Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Java » Distributed Java
Bookmark "The difference of start rmiregistry by API and Command line" Watch "The difference of start rmiregistry by API and Command line" New topic
Author

The difference of start rmiregistry by API and Command line

Junfeng Cui
Greenhorn

Joined: May 10, 2004
Posts: 2
The problem is that if I start rmiregistry by command line, the binding class will throw out ClassNotFoundException.
But if I use LocateRegistry.createRegistry(1099);, it will work.
I do not know what's the difference.

Thanks.
[ August 17, 2004: Message edited by: Junfeng Cui ]

Junfeng Cui
Junfeng Cui
Greenhorn

Joined: May 10, 2004
Posts: 2
I figured out why... a dumb question.
I've started rmiregistry in two jvms.
Kedar Bhawarthi
Greenhorn

Joined: Jun 21, 2004
Posts: 10
I don't understand what you mean by two JVMs?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: The difference of start rmiregistry by API and Command line