Creating a remote EJB client

Creating a remote EJB client for the WildFly application server is very similar to AS7. The big difference can be noticed between AS6 and newer releases.

As a matter of fact, previous versions of WildFly (JBoss AS versions before 7.x) used the JBoss naming project as the JNDI naming implementation, so developers are familiar with jnp:// PROVIDER_URL to communicate with the application server.

Starting with AS7, the JNP project is no longer used—neither on the server side nor on the client side. The client side of the JNP project has now been replaced by the jboss-remote-naming project. There were various reasons why the JNP client was replaced by the jboss-remote-naming project. One of them was that the JNP project did not allow fine-grained security configurations while communicating with the JNDI server. The jboss-remote-naming project is backed by the jboss-remoting project which allows much more and better control over security.

Besides the new naming...