Hi friend,
Yes, thanks. I changed the policy file and gave the permission to bind an object. It worked well ! But now I get this exception :
 
java.rmi.ServerException : RemoteException occured in server thread; nested Exception is : java.rmi.UnmarshalException : error
unmarshalling arguments; nested exception is : java.lang.ClassNotFoundException : Test_Stub !!!
 
The problem is that Test_Stub already exists in server side jar file (TestEJB.jar) !!! Of course because I'm using pure 1.2, I've used
-v1.2 option for RMI-Compiler (so it didn't generate the skeleton files). Can it cause any problem ?
 
Best Regards,
Armond
 
----- Original Message -----
Sent: Thursday, October 28, 1999 10:39 AM
Subject: Re: Binding in RMI Registry !

Hallo,
the error message shows that you dont have the permission. You can grant yourself the permission by entering the permission into the policy file
Hermann Schmitt
----- Original Message -----
Sent: Wednesday, October 27, 1999 9:12 PM
Subject: Binding in RMI Registry !

Hello,
 
Are session beans allowed to bind a rmi remote object (which implements java.rmi.Remote) into RMI registry ?
I tried to do it in order to able to share a static data among server side beans ! but unsuccessful and got this
security exception :
 
java.security.AccessControlException : access denied (java.net.SocketPermission localhost : 1024- listen, resolve)
 
Is there any solution that a bean can bind an remote object ?
 
Thanks in advance,
Armond
 
 

Reply via email to