Hi Richard,
 
The client.jar seems to be out of sync with server.jar. Could you kindly check that client.jar you are setting in the classpath is from INSTALL_DIR\server30\lib\server. If this is the case then a work around can be achived by putting INSTALL_DIR\server30\lib\server\server.jar(Instead of client.jar) in the classpath of the client.
 
In your java client please set the System.SecurityManager as,
public static void main(String args[]){
        System.setSecurityManager(new com.pramati.security.client.RMIClientSecurityManager());
        ......
        ......
}

This is to enable dynamic downloading of IMPL_stubs(Home and Remote stubs).
 
If you are putting MyApp.jar and MyAppClient.jar from INSTALL_DIR\server30\nodes\StandAlone\default\archives\MyApp.ear\classes in the client's classpath, then you need not set the security manager.
 
This weekend we are planning one more upload to support jar deployment, deferred primary key support and minor bug fixes. Please let us know if the same problem recurs. It would be a great help to us to resolve all the problems before the coming upload.
 
Thanks & Regards,
 
Gautam
Server Team
 
 
 
> Can you provide an example of calling a deployed EJB from a pure
> java client app?
>
> Here's what I tried...
>
>
> naming environment:
>
>
>
java.naming.factory.initial=com.pramati.naming.client.PramatiClientContextFa
> ctory
> java.naming.provider.url=rmi://127.0.0.1:9191/
>
>
> -classpath client.jar;jaas.jar;MyAppClient.jar
>
>
> result:
>
> "javax.naming.ServiceUnavailableException: Unable to get
> RemoteNameServer : java.
> io.InvalidClassException: com.pramati.util.ProtonUnicastRef; Local
> class not com
> patible: stream classdesc serialVersionUID=-2937931484566183960
> local class seri
> alVersionUID=-5703586549380452216"

Reply via email to