| Author |
RMI client side compilation
|
Jan Groth
Ranch Hand
Joined: Feb 03, 2004
Posts: 456
|
|
hi there, i'm in the midde of my RMI "hello world" equivalent. the server is up and running, stub / skeletons are generated. i've a problem understanding the mechanism / code base the client needs. here's my setup: server side - interface MyService - class MyServiceImpl - class MyService_Skel (-class MyServiceRegistration) client side - class MyService_Stub (manually copied over from server) - class MyServiceClient My problem is the compilation of the MyServiceClient. In the examples I'm stepping through, the knowledge about a MyService object is required. I don't see how the client can obtain this knowledge, without (manually) copying the interface from the server. Is this what I'm supposed to do? Does RMI require two equivalent interfaces on both sides, server and client? Many thanks for helping me out... Jan
|
 |
Avi Abrami
Ranch Hand
Joined: Oct 11, 2000
Posts: 1112
|
|
Jan, If both client and server JVM's are both, at least, JRE 1.2, then you don't need the "skel" file. Both client and server must have the "stub" and remote interface classes. Hope this answers your question. Good Luck, Avi.
|
 |
 |
|
|
subject: RMI client side compilation
|
|
|