In a J2EE application, clients (applications, JSPs, servlets, JavaBeans) access entity beans via their remote interfaces. Thus, every client invocation po
In RMI lingo, the skeleton is the generated object that sits on the server, accepts calls from the network, unmarshals them, and forwards them on to the business object.
So....
Client Business Object -> Stub -> Network -> Skeleton -> Server Business Object
It's a rather antiquated term, though, since this sort of stuff is much more automated than it used to be in early java, where skeletons had to be explicitly generated.