Application deployed as an ear fails, but succeeds when deployed exploded. -------------------------------------------------------------------------- Key: JBAS-2360 URL: http://jira.jboss.com/jira/browse/JBAS-2360 Project: JBoss Application Server Issue Type: Bug Security Level: Public(Everyone can see) Components: Deployment services Affects Versions: JBossAS-4.0.3 Final, JBossAS-4.0.3RC2 Environment: GNU/Linux (Fedora Core 4); kernel 2.6.13-1.1526_FC4, i386. Reporter: Stephen Saucier When application is deployed in a directory with a suffix of .ear, it deploys fine. When application is deployed as a jar file with a suffix of .ear, it complains that my ejb-jars are invalid, with an error message ending " is not an EJB .jar file!" My ejb-jar files contain only the EJB bean implementation class files (and deployment descriptors), the interfaces and other supporting classes are packaged in a ejb client jar, and are referenced by the ejb-jar using a Class-Path entry in the Manifest. This should be a valid mechanism for deployment, according to the ejb 2.1 spec. I'm pretty confident that the standard deployment descriptors are without problem since this application was previously running on a different application server, but it is possible the problem is coming from one of my jboss deployment descriptors (but I doubt it). Additionally, since the application deploys fine when not deployed in a jar file but in a directory, I don't think the problem is coming from my application. I followed the directions on the wiki to restore J2EE compliant classloader behavior.