My guess is that JBoss can't find this exception class during EJB deployment even though it is in your WAR file. (btw: jars are deployed before wars)
Solution: pull out your Exception class and all other classes which are used in both war and jar into a separate jar file which you include in your ear and adjust the CLASSPATH in your Manifest files to refer to this "shared jar". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3909225#3909225 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3909225 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
