Unable to access jars that are common to both web module and

[hari_mails]

Hai all,
JBoss Version: 4.0
I have created a common.jar file, which is common to both web module and ejb module. And I created an ear file that contains web module (.war), ejb module (.jar) and common.jar file which is placed in the lib directory of the ear file as shown below. I'm adding the manifest file by setting the classpath to common.jar file both in web module and ejb module. But I'm unable to access that common.jar in both web module and ejb module.

The folder structure for ear file:

META-INF/
META-INF/MANIFEST.MF
META-INF/application.xml
ejb.jar
web.war
lib/
lib/common.jar


The manifest file in the web.war includes:

Manifest-Version: 1.0
Class-Path: ./lib/common.jar

The manifest file in the ejb.jar includes:

Manifest-Version: 1.0
Class-Path: ./lib/common.jar

Even then IÂ’m not able to access the common.jar file in web.war and ejb.jar. So, I added manifest file in the ear file also while includes the following

Manifest-Version: 1.0
Class-Path: ./lib/common.jar



2. Unable to access class files, which is common to both web module and ejb module


The folder structure for ear file:

META-INF/
META-INF/MANIFEST.MF
META-INF/application.xml
ejb.jar
web.war
classes/


The manifest file in the web.war includes:

Manifest-Version: 1.0
Class-Path: ./classes

The manifest file in the ejb.jar includes:

Manifest-Version: 1.0
Class-Path: ./classes

Even then IÂ’m not able to access the common.jar file in web.war and ejb.jar. So, I added manifest file in the ear file also while includes the following

Manifest-Version: 1.0
Class-Path: ./classes

Should I need to do something else to get it work.

Regards,
Hari

[meatus]

I'm having a very similar problem since upgrading to 4.0. I have a significant amount of development work working under 3.2.4/6, and I thought it was time to upgrade. Now, none of my archives seem to be part of the classpath. The only applicable note I've found so far was on the Wiki which says something like, "the classloader scheme has changed in 4.0, try running the 'standard' server implementation for something closer to 3.2.x." I deployed my stuff to standard and ran it, and, sure enough, everything worked fine.

I've tried several different solutions, including the manifest classpaths that you mentioned, but with no luck. If nothing else, I think the 4.0 administrators guide is supposed to be released soon.

Wish I could be more help,
Brett