For launching GlassFish app clients, the JRE already on the client's system will launch the app.
Just for completeness, things can be a bit different for other Java Web Start applications that are launched from a server running the Java Web Start example servlet that comes with the JRE/JDK. That servlet has a feature that will download the JRE if needed. Currently the servlet that handles GlassFish app client launches does not do that. The JRE on the client is what's used.
The usual rules about the PATH setting, etc. apply. If a client-side user were to enter the javaws command, then whatever executable that resolves to is the one that will run with the associated Java libraries. If the end-user specifies the full path to the javaws image, then that one and its associated libraries are used.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=221270