Hi.
At runtime an app client launched using Java Web Start will have access to only those JARs that are in the Java runtime, in the downloaded app server JARs needed to run the app client container (such as appserv-rt.jar and a few others), and any JARs packaged with the app client.
The Java EE spec, in section 8.2, describes the ways in which library JARs can be made accessible to your code. In particular, the spec does not provide for a way to bundle libraries into a stand-alone client module. Because that's what you have built, GlassFish is not paying attention to the SwingX JAR (even if it is included in the client JAR that NetBeans creates.)
One thing you could do is to create an EAR that contains the app client module in it. You can then add the SwingX library to the EAR. By default, GlassFish will make any JARs in the /lib directory of the EAR available to all submodules - including, in your case, the app client.
Please try that and see if it works better for you. And let us know the results.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=210920