Hi, Jim.
I assume you are using the automatic built-in support for Java Web Start (as opposed to your own JNLP).
Are you packaging the app client as a stand-alone module or inside an EAR?
This should work automatically if you package the app client and the 3rd-party JAR into an EAR. Make sure that either (1) the 3rd-party JAR resides in the /lib directory of the EAR (or, if your application.xml specifies <library-directory>, whatever you set that to) or (2) the app client JAR's manifest refers to the 3rd-party JAR using a relative path within the EAR.
In either case GlassFish should make the JAR accessible to the app client, whether you launch it using the appclient script or using Java Web Start.
- Tim
[Message sent by forum member 'tjquinn' (timothy.quinn_at_sun.com)]
http://forums.java.net/jive/thread.jspa?messageID=379669