Originally posted by Andres Gonzalez:
here's my first guess..
I have doubts in Dog and DogTrainer Interface. I put Dog in both because the book mentioned somewhere that the class file must be available in the other side (server).
And the DogTrainer interface in both because the remote object and the stub (in client) implement the same interface.
am I completely lost?
Originally posted by Edward Tse:
My guess to why stub are so important is because even though the programmer is only dealing with an interface, however, the remote object will still serialized and transfer over the network. Without the stub, client side has no way of knowing how the remote object should look like.
Howdy! I am about 30 minutes away from posting PDFs of all the sharpen answers that aren't in the book (we leave them out of the book for the sake of instructors).
I'll give the link here when I'm done posting them...
Originally posted by Bob Walker Jr:
I don't get it. Why is the stub skeleton issue so important?? They are transparent to the application programmer. In fact, the client only needs classes/interface that it uses (references in the code). Everything else is managed by the RMI infrastructure. When I package my EJBs for clients, I DO NOT put stubs in there. All I put is the home and remote interface classes (and other value object classes). That's it. Stubs classes are marshalled to the client by the RMI framework as needed. That's the job of PortableRemoteObject.narrow().
Is it not so??
Originally posted by Bharat Ruparel:
I am not sure where to find these links. Please let me know.
Thanks and Regards.
Originally posted by Wally Flint:
Thank you very much. And now for your review... oh, uh... first just one little bitty question - how come Bharat's a ranch hand, you're a sherriff, and I'm only a greenhorn?