You must package the WAR and the EJB jar into an EAR file inorder to access EJBs via local interfaces from a servlet. As an alternative, the remote interfaces are optimized, thus the use of the local interfaces are probably not necessary. We use the EAR file approach with great success.
Hope this helps
Thanks a lot for your reply,
I had read about what you say, but I also use Pramati Studio J2EE IDE builtin J2EE server and it is capable of deploying separate jars and wars without any problem.
In development time, it is much faster to be able to deploy just the files you change. that is why I was looking for a way to do it in JBoss.
You can do that. But you must use remote interfaces not local interfaces.
During development I deploy war and jar file with no problems. I don't have to make changes whether I place the jar & war into an ear or separately. For even quicker development, use Jboss' ability to deploy to a directory that *looks* like the structure of the archive you're deploying. It's very simple and it sped up my development (huge project) by a factor of 10.