Monday, July 14, 2014

EJB v3 Client for JBoss Gotcha!

If you are writing a standalone client for either a local or remotely deployed EJB v3, and face the following issue:

javax.naming.CommunicationException
[Root exception is java.lang.ClassNotFoundException: org.jboss.ejb3.proxy.JBossProxy
(no security manager: RMI class loader disabled)]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:788)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
at javax.naming.InitialContext.lookup(Unknown Source)

...


The simple fix is to include 'jbossall-client.jar' in the client classpath.

No comments: