So could you try removing the Class-Path from this MANIFEST.MF of the EJB jar? We have
known some issues where the MANIFEST.MF Class-Path entries caused EJB3 deployments to
incorrectly deploy the artifacts.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244693#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...