File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Distributed Java and the fly likes Rmi basic, why skeleton is not needed ? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Distributed Java
Bookmark "Rmi basic, why skeleton is not needed ?" Watch "Rmi basic, why skeleton is not needed ?" New topic

Rmi basic, why skeleton is not needed ?

Ranch Hand

Joined: Nov 22, 2008
Posts: 18944
I am beginner to RMI,
Why we need to place stub files generated after executing,
rmic -v1.2 BookServerSide
BookServerSide_stub.class to both client & server side ?
As i know, stub file is a representation of server side object over the
client side, to which client pass the request.
If i dont put the stub file over the server i get an exception
java.lang.ClassNotFoundException: BookServerSide_Stub
even though i agree to a point, how server will come to know client ? Why we dont generate skeleton file as in jdk1.1 ?
from ,
Jerry Pulley
Ranch Hand

Joined: Sep 19, 2000
Posts: 221
Please read the JavaRanch policy on user names at, and register a user identity with a complete first and last name.
I'm working on an answer to your questions about stubs on the server and how unmarshaling works without a skeleton; now that I'm at that point in my Developer project I feel like I ought to know too. In the meantime, any RMI internals expert please feel free to help us out here!
Ahamed Aslam.K

Joined: Nov 23, 2004
Posts: 1
I also had the same doubt before... i have found the answer to this question myself after a lot of experimentation and research.. just check out the link
I agree. Here's the link:
subject: Rmi basic, why skeleton is not needed ?