This issue seems to be related to the order of the JAR files listed in the Class-Path of the manifest file. We had a similar issue in 3.2.3, and reordering things in the Class-Path reolved it.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3846374#3846374 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3846374 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
