Hi, Danny.
You posed several questions. Maybe I can help with at least some of them.
First, try to narrow down whether the problem is related to GlassFish itself or with the NetBeans-to-GlassFish interaction. If you build your application using however many NB projects you have, and then use the GlassFish command line or admin GUI to deploy the application, do things then work correctly?
As for using Java Web Start to launch the client... If you are using the support that is built into GlassFish for launching app clients using Java Web Start the JNLP you have added to the EAR will not be used. If you are using your JNLP to try to launch the app client, this may be part of the problem. A true Java EE app client must run in the app client container (ACC). The ACC prepares the environment correctly for the app client and runs automatically if you use the appclient script or launch using the built-in support for Java Web Start. It is not possible - well, at least not supported - for developer-provided JNLP to launch the ACC to run an app client.
It is certainly possible to write your own JNLP to launch a client program (although not a true Java EE application client) that could explicitly look up the server-side components and contact them. But it's much easier to use injection that's available in an actual app client which the ACC takes are of for you.
Does this help some?
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=228774