• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
Sheriffs:
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
Bartenders:
  • Mike London

Use of remote Interface in RMI

 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I have small query regarding the remote interfaces used in the distributed java (RMI and EJB). When we lookup the remote object, why the type cast is done as RemoteInterface. and what is the content of Stub and Skeleton. Please explain this process clearly.

Thanks in Advance.
Deepak
 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The stubs and skeletons are used to identify the remote connection and session, specifically the location of the distributed objects. This includes ports / ip address / naming information, etc...

In fact, you can examine the contents of the stub and skeleton using a decompiler or a hexeditor. You'll see meta information regarding the location of the objects.

Originally posted by Deepak Vernekar:
Hi,

I have small query regarding the remote interfaces used in the distributed java (RMI and EJB). When we lookup the remote object, why the type cast is done as RemoteInterface. and what is the content of Stub and Skeleton. Please explain this process clearly.

Thanks in Advance.
Deepak

 
reply
    Bookmark Topic Watch Topic
  • New Topic