Even with J2EE 1.4 would recommend a servlet.
I still do.
Thank you for the quick answer, but the problem is that I need to access from a rich-gui swing applet, i.e. I need to obtain some EJB entities from the server, and then paint the information in a rich-gui application (each type of entity would lead the painting of the related GUI-Object), and as far as I know I can't do that in plain HTML, but with swing I could do almost anything rich-gui.
for me this worked for swing apps as well as JUnit tests (which run in separate JVM).
1) add to java installation where the server is running: lib/security/java.policy the following line in grant section:
2) on the client in java somewhere in a init method
RMISecurityManager securityManager = new RMISecurityManager(); System.setSecurityManager(securityManager);
then resolve the remote interface as usual.
Thanks for the trick wauwau0977, I'll try.
clebert.suconic, could you tell me why don't you recommend an Applet please?, in my case, as I told you, is not an option, but a requirement?
I'm having the same problem.
My application works great when it's a full standalone client, but when changing it to an applet, the jndi always returns a javax.naming.reference object instead of returning a bean like it normaly should.
wauwau0977, I tried what you said, but it does nothing. My policy is already set to grant all (which helped with other problems by the way), and the RMISecurityManager did nothing on the client.
However, I'm running on the same JVM as JBoss, could this be the problem ?
Any help is appreciated ;)