The easy thing is to copy all of client/*.jar. Another alternative is to look at the manisfest.mf file within jbossall-client.jar and copy only the files mentioned. A third option is to copy only the JAR files you need for your app. Yes, I know, having all the necessary classes within jbossall-client.jar was convenient so that you did not have to think about such things. By the way, check out JBoss Tattle - it will give you a list of JAR file dependencies which should made it fairly easy to determine which JAR files you will need. The JBoss team made this change because of the difficulty in keeping the contents of jbossall-client.jar in synch with the rest of the JAR files, especially in the common situation when an updated component (such as EJB3 or messaging) is released and suddenly the classes packaged in jbossall-client.jar were not compatible with the classes in the updated JAR files. Having jbossall-client.jar not contain the classes but instead just reference the JAR files solves this problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222060#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...