• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

rmi.server.codebase

 
Tim Adam Cooper
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a couple of questions about the property as below:
rmi.server.codebase
Question1: Is this property really only used for the client side only and not the server?
Question2: Is this property really only for downloading the stub classes?
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'll just answer #2 as this will show you you don't need an answer to #1.
#2, yes it is only for dynamic downloading, so you don't need to use codebase. Especially when you make the server and clients into executable jars.
Mark
 
Anonymous
Ranch Hand
Posts: 18944
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mark,
Seems like the optimum solution would call for the client having no knowledge of the server stubs in its classpath, the server would serialize them when asked, annotating them with a codebase.
Does the process of creating executable jars (I haven't gotten to this point yet) include the stubs in the clients jar file?
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes the stubs will be included in the client jar file.
there nowhere you will need codebase at all.
and serialization occurs under the hood, meaning you don't have to make anything implement Serializable, the will have interfaces extend Remote and other extending UnicastRemoteObject
Mark
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic