Personally, I'd communicate with a servlet. This _is_ a level of overhead, but at least you have some level of confidence that you'll be able to get through firewalls.
Thanks, the more I read about this, it seems that applet-servlet-EJB is the way to do it. Anything else seems to be more of a hack.
However, if anyone has any other opinions on this, I'd love to hear it.
I also want to access ejb from an applet over http-port. My idea was to use the apache-soap interface. My client calls a remote method over the soap protocol. The called method is in a package implemented as web service on the machine where also jboss/embedded tomcat are. The called method looks up for the bean and returns the bean to my applet. So far my idea. If I try to access my ejb directly from the client it works fine, and if I test my web service over soap without bean access it works fine, too. But all together doesn't work. I get a ClassNotFoundException for my home interface of the bean. Is the only way to access ejb from an applet really the access over a servlet?