I included all RMI stub classes in the client jar file to avoid configuring codebase, policy file and security manager. Everything works perfect on all OS I tested: Linux, Win2k, WinXP, Mac.
SCJP,SCJD,SCWCD,SCBCD,SCDJWS,SCEA
I have bypassed all of these configuration when I put the stubs accessible from the client's class path
SCJP,SCJD,SCWCD,SCBCD,SCDJWS,SCEA
The Sun Certified Java Developer Exam with J2SE 5: paper version from Amazon, PDF from Apress, Online reference: Books 24x7 Personal blog
may not be possible to use external RMI Registry
since stubs are local to client, if ever you change server side, you will have to provide clients with new stubs (rather than the client dynamically downloading them as required).
(you really read all of these messages! amazing)
[Andrew] may not be possible to use external RMI Registry
[Marcos] why? anything related to security policy?
[Andrew] since stubs are local to client, if ever you change server side, you will have to provide clients with new stubs (rather than the client dynamically downloading them as required).
[Marcos] This is because the client is tied to a specific remote interface but the server can use different implementing classes and the client will download them as needed?
The Sun Certified Java Developer Exam with J2SE 5: paper version from Amazon, PDF from Apress, Online reference: Books 24x7 Personal blog