Rmi basic, why skeleton is not needed ?

[Anonymous]

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 ,
vikram.

[Jerry Pulley]

Vikram,
Please read the JavaRanch policy on user names at http://www.javaranch.com/name.jsp, 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!
Jerry

[Ahamed Aslam.K]

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
http://aslam128.topcities.com/rmi.htm