OK, I solved the problem. The actual exception was a VerifyError on a JDOM class. So, its a class loading issue. (there's a class that is not in the old jdom.jar that ships with JBoss 3.2.3 in /lib that the CMS stuff needs (org.jdom.Content) - this class is in the new jdom.jar that is found in the CMS sar.
I just copied the jdom.jar from the cms sar to the JBoss /lib directory. In effect, updating the jdom.jar that comes with the JBoss 3.2.3 to a newer version. The sar deployed successfully when I did this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876637#3876637 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876637 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
