That's just what I meant with "client jar". You have to deploy parts of your application - see erez' mail below - with your client software so that the client can talk to the server. Yes, RMI can do this automatically, but I am not an RMI specialist, too. Maybe there is some RMI specialist in the JOnAS team that can give you a hint how to do this automatically. But since J2EE comes with JavaWebStart in the near future, the question will be if you will need this. The other question is, how often you think that you want to change your server application? And even if you change it often, why not putting that client jar onto a single common server file share, that will be accessed by the client? Then you do not have the replicate it. Another way is that e. g. WindowsNT has internal Server to Client broadcast file replication mechanism, there you have to put it into one directory on the server once, and NT deploys the file automatically. So this should not a big problem, as I think.
Markus
----- Original Message -----
From: SG
Sent: Wednesday, August 08, 2001 8:24 AM
Subject: Re: Still have problem with not using config_env

Wow, are you serious? I actually need the stubs on my client's computer? I thought RMI could send the stubs across the network? (I am new to RMI) I may be completely missing this though. So, then are you saying that everytime I deploy a bean, I have to give the stubs to a client? (Whether that be JSP, another EJB server on another comp. or some other company's app)
 
Thanks for the reply. If there is no way to send the stub across RMI, then this solves alot of questions but not problems. (What about dynamic class loading with RMI? Is there a way for the client to try the call, and then if it doesn't have the stub, to ask the RMI Registry to send the stub?)
 

Reply via email to