• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

RMI client side compilation

 
Ranch Hand
Posts: 456
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
Ranch Hand
Posts: 1143
1
Eclipse IDE Oracle Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
    Bookmark Topic Watch Topic
  • New Topic