JBoss, exploded jar vs compact jar

I am working on Java 1.6, JBoss 5.1, EJB 3, and Hibernate开发者_开发知识库 2. Every time I deploy the ear, if the jar is a compact one (non-exploded), application doesn't work. However when I explode the jar and then add it to the ear, the app works fine. Tried restarting Jboss, doesn't help.

The ear refers to numerous external jars; would the order of loading the jars be an issue? How can I make JBoss load external jars followed by the app jars?

Thx. WM.

How exactly does it fail? Nobody can help you if you don't tell the symptoms.

In any case, I'd be just happy that your application works, one way or another :) There is nothing wrong with exploded jars, AFAIK.

JBoss's class loading mechanisms sometimes lead to unexpected issues. I fixed this using a classload-repository

<jboss-web>
   <loader-repository> 
      com.example:archive=unique-archive-name 
   </loader-repository> 
</jboss-web>