How to setup JNDI for Glassfish 3.1.2 for a stand-alone client?

Question

I try to connect from a stand-alone swing client (running in a separate JVM on the client machine) to the Glassfish server.

I currently use the following settings fr

Answer 1

By looking into the MANIFEST.MF file of the gf-client.jar library I noticed that there are some dozen other jar-libs referenced from there. In order to run the client outside of the netbeans platform, I had to copy all these libs to the final build of my own application. Then it works just fine... :-)

Answer 2

You are missing the jar containing the class com.sun.enterprise.naming.SerialInitialContextFactory in your classpath. Add it to the manifest of your client jar.

Answer 3

A point to clear about Remote EJB interfaces

You want a Remote EJB interface when your client application lives on one JVM different than the one hosting the EJB module. In other words:

• The client application lives on one JVM and the EJB module is deployed on another JVM on the same machine

OR

• The client application lives on one JVM and the EJB module is deployed on another JVM on a remote machine.

For simplicity sake

Lets consider the first scenario where both of the client app and the EJB module live on different JVMs on the very same machine.

1. Make sure you have 2 JDKs installed on your machine.
2. Deploy the EJB module in a Glassfish installation pointing to one JDK (JVM). We can agree to install Glassfish in "C:/glassfish3/"
3. According to the documantation in this link. Add to your client application classpath the file "gf-client.jar" as an external library from within the installation directory (i.e. C:/glassfish3/glassfish/lib/gf-client.jar) rather than copying it.
4. Also add to your client application classpath the file remote_interface.jar includes the Remote business interface of your EJB.
5. Run the SE (stand alone) client application on the second JDK (JVM)

An important tip about the client

As per the documentation, stand-alone java clients must explicitly use the global JNDI name to lookup the Remote EJB. Also, Glassfish does not need any properties instialization to invoke the InitialContext() constructor. Thus the client application can invoke the EJB using the following snippet:

InitialContext context = new InitialContext();
_RemoteEjbInterface ejbBean = (_RemoteEjbInterface) context.lookup("java:global/DeployedEJBAppName/EjbImplClass!com.sam._RemoteEjbInterface");

In case your SE stand alone client application is a maven one then you need to

1. Account for the above step (3) by adding this entry to your client app POM:

   <dependency>
       <groupId>org.glassfish.main.appclient.client</groupId>
       <artifactId>gf-client</artifactId>
       <version>3.1.2</version>
       <scope>system</scope>
       <systemPath>C:/glassfish3/glassfish/lib/gf-client.jar</systemPath>
   </dependency>
   

2. Account for the above step (4) by a POM dependency pointing to you remote_interface.jar in your local maven repo assuming you installed it. Follow this to know how.

Another documentation to reference is here