One other quick thought about this...
Is there a chance that one of the JARs that the client depends on has no manifest? The NestedAppClientDeployer used to assume that every JAR on which the client depends (whether directly or indirectly) contained a manifest. I fixed that a while ago - back in January - which was after the release of GlassFish 3.0.
If you use any promoted built of 3.0.1 (more stable than 3.1) that particular change should be there.
- Tim
[Message sent by forum member 'tjquinn']
http://forums.java.net/jive/thread.jspa?messageID=473806