Where is the Stub created? In registry or in Client's machine?

Question

Hii..
I hav some doubts abt RMI..
The part after t client getting t remote ref(stub obj) of t client s perfectly clear 2 me.
My doubt s abt t previous part � ie. How t client gets t stub obj.
I ll tell my concept abt this� plzz correct me if I m wrong.. :
Suppose Rmiregistry n server(which extends from UnicastRemoteObj)runs on t same m/c
Client runs on another m/c
1. Wen server s up, it exports itself 2 a particular port n listens 2 t port for incoming client connections.. (this port s chosen arbitrary@runtime)
2. Rmiregistry listens 2 port 1099 on t same machine..
3. Server registers a public name wit registry n pass t a Remote obj(server obj) as t second param in t bind/rebind call
4. Rmiregistry itself s a remote object.. For accessing any remote object we need a stub.. t Naming class act as t stub for rmiregistry
5. Now t situation s client needs 2 get an obj of stub 2 contact t server, or at least it shud know 2 which arbitrary port t server s listening 2
6. so it looks up t rmiregistry for t public name, t rmiregistry creates an object of stub and returns t stub object 2 t client..(is it right?)
7. For creating an obj of stub, rmiregistry must know 2 which port t server is listening(so t server might hav given t info 2 registry while binding.. right??)
8. since rmiregistry itself is a remote object t newly created stub object itself is passed in a serialized manner(registry marshals t stub obj) 2 t client using t rmi protocol itself.
9. now t client demarshalls t passed stub obj 2 get t stub
10. finally t client uses t stub 2 directly communicate wit t server(ie. 2 connect 2 t listening port of t server)
11. now t commn b/w client n server takes place directly without t intervention of t rmiregistry�
This s my Concept abt t whole scenario in 1.4(in 1.5 no need 4 stub or skeletons) plzz correct me if I m wrong@any of these points..
If my concept is right, then I hav a few q�
Consider an application Calc
� remote interface : Calc(which extends Remote)
� server which implements t Calc i/f : CalcImlp(which extends UnicastRemoteObject)
� client : CalcClient
In CalcImpl�s main(),
Naming.bind(�calc�, new CalcImpl())
In CalcClient,
Remote r=(Calc)Naming.lookup(�rmi://host:1099/calc�);
My doubt is that t server s passing an obj of CalcImpl 2 t registry in Bind fn and wat t client s getting wit lookup fn s actually an obj of CalcImp_Stub which t rmic generated. So does t rmiregistry uses Reflection 2 get t name of CalcImpl n then add a �_Stub� 2 t name it got and searches for that class??
I hav been checking so many books 2 check whether my concept s right or wrong..
But I didn�t any info from anywhere.. all of those docs say how 2 do it� None of them say what s happening inside�
Plzz help me...

Answer 1

Please don't use this sort of SMS speak "thnx 2 u" when asking a question. If you haven't sufficient respect to spell it all out, why should we make the effort to reply?
I've not tried to read through all that butchered English, but in brief:
Stubs can be created at compile time, or with Java 5 they can be dynamically created on the client in communication with the server.
In the former case, they can either be distributed with the client application or downloaded from a specific URL. It is up to you to specify the URL and make it available. It is not the job of the registry.
In the latter case you won't need to do anything special.
If you want a good book which covers this in detail, I recommend the William Grosso RMI book. This is pre-Java 5, but covers the internals of the RMI mechanism in a lot of detail. Hopefully a new edition will be issued to cover Java 5.
Dave.