Originally posted by Dan Myers:
Question1:
I do not understand the posts on rmi.codebase or CLASSPATH and whats the difference.
Question2:
When do i need to use rmi.codebase?
When you are doing dynamic loading of your stubs... I did not use that in my project.
Originally posted by Dan Myers:
Question3:
Whats wrong on my plan described below (CLASSPATH)?
- I want to packaged two jar files, one for the server, one for the client.
Both jar files contain all classes but
a)server.jar doesnt contain client classes
b)client.jar doesnt contain server classes
For clientstart:
- Before startup, user sets the CLASSPATH to the client.jar
- user starts client
For serverstart:
- Before startup, user sets the CLASSPATH to the server.jar
- user starts server
Comments please ...
I did not have to set a classpath for anything... just used executable jars and told that accessor to run them from the install directory of my submission.
One note on you packaging above... you client will need to know about your stubs and interfaces so that your RMI stuff will work right, but you probably already knew that... I just couldnt tell if they were included in the client jar