1 of 1 people found this helpful
Container specific client jars are needed on the client side.
You can add the *"$JBOSS_HOME/bin/client/jboss-client.jar"* in your client classpath. Without this how your EJB client will find the reference of the Context.INITIAL_CONTEXT_FACTORY implementation like "org.jboss.naming.remote.client.InitialContextFactory" and other container specific jars which contains the remote invocation protocol implementation like "http-remoting://"
Also if you are using the "ejb:/" ejb namespace in that case as well as the ejb: namespace implementation is provided by the jboss-ejb-client library, and allows the lookup of EJB's using their application name, module name, ejb name and interface type, You must use it, you must have the appropriate jars on the class path.
Thank you for answer!
I'm kind of new to remote EJB's, and I was under the impression that there was a unified way to call them through the jee-api for all the different application servers.
So basically each appserver has it's own invocation-protocol and InitialContext-factory and in order to invoke remote EJB's you need different client-api's for every different appserver you want to call? I guess this applies to remote spring-beans as well?