ansaurus

Question

Answer 1

A:

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.

Nikita Rybak 2010-05-04 19:58:49

Thanks for the reply. The deployment doesn't go to completion. Fails to lookup the external jars.

Win Man 2010-05-04 20:05:37

Any stacktrace and error messages to google for the answer?

Nikita Rybak 2010-05-04 20:19:56

bcprov-jdk16-144.jar.org.bouncycastle.crypto.macs] <IMPORT-ALL>NON_EMPTY}} at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:448) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:169) at $Proxy173.<clinit>(Unknown Source)

Win Man 2010-05-04 20:27:23

Nikita, the above information was only one relevant. Not much information in the logs other than, deployment failure.

Win Man 2010-05-04 20:31:56

Nikita Rybak 2010-05-05 00:36:55

True. None whatsoever. For now I am running the app with exploded jars and wars. Thanks for your help Nikita.

Win Man 2010-05-05 16:50:56

Answer 2

A:

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>

stacker 2010-05-04 20:04:07

ansaurus

tags:

views:

answers:

JBoss, exploded jar vs compact jar.

related questions