Win a copy of Head First Android this week in the Android forum!
  • 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 ...
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • Al Hobbs
  • salvin francis

How RMI is working without Skeletons?

Ranch Hand
Posts: 59
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

RMI might be old topic, but i am referring it before going to EJB.
From the reference of Head First Java, which is very old book, i know that the communication between client and server is being done with the help  of stubs and skeletons that are generated with the rmic tool.
But when i tried the example,
1. rmic is giving this warning, i think it's telling about some updates in RMI, but i didn't understand what is meant by static and dynamic stubs here:
Warning: generation and use of skeletons and static stubs for JRMP is deprecated. Skeletons are unnecessary, and static stubs have been superseded by dynamically generated stubs. Users are encouraged to migrate away from using rmic to generate skeletons and static stubs. See the documentation for java.rmi.server.UnicastRemoteObject.

2. rmic have generated only stub class but not skeleton, but still the application is working fine. How application is working without skeleton at server side?

Thanks in advance.
Saloon Keeper
Posts: 24553
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The original concept was to provide a lightweight remote-enable API on the client side and a corresponding implementation class on the RMI server side. It has been a long while, but if my memory isn't too bad, the "skeleton" was an RMI-enabled prototype implementation of the client API that you were expected to flesh out with the actual functioning application code.

Basically, that has been replace by a simpler and more straightforward mechanism where by means of introspection and implementation of RMI-friendly classes and interfaces, the RMI process can do the job once done by RMIC by working backwards from the RMI implementation classes. So RMIC has become redundant and obsolete.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic