Yes, the issue refers to v3 (and it has been fixed in v3).
Changes to the appclient script have no effect on clients launched using the built-in support for Java Web Start.
Could you please try this: Add the EclipseLink jar to the domain's lib/ext directory. Add to the client JAR's manifest a dependency on the EclipseLink extension. This will allow the built-in Java Web Start support in GlassFish to detect the dependency and make then make sure the EclipseLink jar is downloaded as needed to support your client.
And of course let us know how this goes!
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=361009