I don't know if JBoss allows you to place the GlassFish JARs in a directory where they will be accessible to applications but not on the path for JBoss itself. That might help avoid the problem with JBoss failing to start.
See the GlassFish package-appclient command. It knows what all the files are that a client would need and creates an appclient.jar file containing them. You could then try expanding that JAR into a JBoss directory as I mentioned above, if JBoss supports such a directory.
- Tim
[Message sent by forum member 'tjquinn']
http://forums.java.net/jive/thread.jspa?messageID=486132