This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have a basic rmi question. After I created the stub for the implementation class of remote interface. Do I need this stub class in the client machine? i.e. To make remote invocations, Does the client need a local copy of the stub class? I think only the remote interface is enough for the client, is that true?
Hi Peter, If you do not have the stubs on the client machine, it will try to dynamically download them via RMI. But you really don't want to do that for the assignment: just package the stubs with the client code and everything will be much easier. Regards, Andrew
Hi peter, FOr the client to operate under RMI mode, it needs the following stuff... The remote interface, the stub and the client class (ofcourse). The server needs the remote interface, the remote implementation class, the stub and the skeleton. Since our assignment requires us to package all in one jar file, the client and the server part will have access to all the RMI stuff required without any need to dynamically download it. If not normally we need to have a http server, or ftp server to serve the stub to the client. They call it the codebase ... If you are interested in RMI, beyond the scope of this project, i would recommend reading Java.rmi by Esmon Pitt & Kathleen McNiff Arun [ September 25, 2003: Message edited by: Arun Kumar ]
SCJP (1.4), SCWCD, SCJD
author and jackaroo