How RMI is working without Skeletons?

Hi,

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.

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.