Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In a J2EE application, clients
(applications, JSPs, servlets,
JavaBeans) access entity beans via
their remote interfaces. Thus, every
client invocation potentially routes
through network stubs and skeletons,
even if the client and the enterprise
bean are in the same JVM, OS, or
machine.
What’s a network skeleton? Some kind of proxy? I understand a stub to be a single use connection, is that correct?
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….
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.