Apologies for not following up sooner. Other things on the to-do list...
Adding the optional extension dependency should have been enough. The Java Web Start support in GlassFish is intended to detect such dependencies and include the corresponding JARs in the set that's downloaded to the client, provided it can find the JARs on the server side so it can serve them.
Interesting point about the javaee.jar. That should have been available on the class path at runtime without you needing to do anything.
It would have been interesting to use the app viewer (javaws -viewer) and see whether the EclipseLink JAR had been downloaded into the Java Web Start cache, and to have inspected the JNLP documents to make sure it was referenced from there.
But, if you're going along fine with a Java client then it sounds like you've overcome this at least.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=361684