users@glassfish.java.net

Re: Standalone client hangs on lookup of remote bean

From: <glassfish_at_javadesktop.org>
Date: Fri, 08 Jan 2010 14:43:20 PST

Log into a system with GlassFish installed. Execute the ${installDir}/glassfish/bin/package-appclient script which creates a JAR file containing the required runtime JAR files.

Then copy the resulting JAR to the remote systems from which you want to run a Java SE client, expand it on those systems, then add the gf-client.jar from that expansion to the runtime classpath for your client. The relative references will all work as long as you do not move the gf-client.jar to some other location on the remote system.

By the way, when you say "stand-alone client" I assume you mean a Java SE client. The term "stand-alone client" is often used to mean "Java SE client" and also is often used to mean "a Java EE application client deployed by itself (not inside an EAR)." You'd use package-appclient in either case to deliver the required JARs to the remote systems; I just want to be sure I understand what you're actually doing.

- Tim
[Message sent by forum member 'tjquinn' (timothy.quinn_at_sun.com)]

http://forums.java.net/jive/thread.jspa?messageID=379714