Originally posted by Mag Hoehme:
My packaging solution was rather easy: The server.jar had the server-side classes, and the client.jar had the client-side classes (that is, GUI and helper classes). But the client required server.jar to be in the classpath.
Some people say that it is necessary to have the stubs in the classpath of the client. This is necessary if you don't want to do stub downloading. The advantage of having the stubs in the classpath is that you don't need to deal with all the security stuff. The alternative is to implement a security manager and download the stubs from the server. (Remember: A Java app is not allowed to accept classes from a stranger - that is, a possibly malicious machine, unless it is explicitely allowed to do so.)
Hope this helps.
I can't beleive you just said that. Now I need to calm down with this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton