Stubs on Client, Server, and packages, et all.
843793Jul 6 2003 — edited Jul 9 2003Although I have no problems setting up a simple example rmi server and client when all classess are in the same package, if I want to mimick a real-life scenario where server and client code are in different packages, written by different developers, little things keep tripping me up. I am missing the correct way of packaging the stuff.
For example. Two computers, cpuServer and cpuClient. On cpuServer I have a directory c:\JavaServer\projectX where the extended remote interface, with its impl, and stub reside. All these sources, including the rmic genned stub, have package projectX as their first line.
On the client, the source and class files reside in an entire different named hierarchy -and package-, yet I still need the SAME stub and Interface from the server. The different package names drives rmic, the client, and myself -crazy.
Hey, this is baby stuff and I am certain that this is no problem, but searching 6 hours thru the forum did not reveal this little detail.
Thank you all!
-nat