The configuration looks good. And i believe you have really packaged it in the war file. Is the exception that you seeing the same as the one you posted in the first post? If not, please post the new stacktrace. Finally add -verbose:class to the JAVA_OPTS section of run.bat (run.conf for *nix OS). This will print out the jar files from which the classes are being loaded. When starting the server redirect the output to some file (the verbose class option prints a lot of information): run.bat > classloading.txt Then navigate to your application to reproduce the exception. Finally open the classloading.txt file containing the logs and search for the offending class. You will find the jar(s) that are being used to load the class. That will give you an idea about what's going on. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219532#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...