I reported that setting the MANIFEST.MF Class-Path did not work in 3.0.2
however at least one contributor to this mailing list assured me that it
definitely does work. Clearly you have evidence to the contrary. I don't use
that anymore. Specify the shared jars in application.xml with the <java> tag
everything loads just fine. I will try this on another platform to see if
it's portable. The java element is definitely portable but my understanding
was that it had to be a bona fide application complete with its own
META-INF/application.xml. In this example the classes in utility.jar are
part of the ear classloader and by extension visible to the EJBs and the
webapp. Why isn't this just stipulated as THE way to share utility classes
among EAR components?
<application>
<module>
<java>utility.jar</java>
</module>
<module>
<ejb>ejb.jar</ejb>
</module>
<module>
<web>
<web-uri>webapp.war</web-uri>
<context-root>/</context-root>
</web>
</module>
</application>
----- Original Message -----
From: "Demyanovich, Craig - Apogent" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 29, 2003 5:05 PM
Subject: [JBoss-user] EAR works in 2.4.10 but not in 3.0.6
> Hello everyone,
>
> Here's the structure of my EAR file:
>
> <root>
> META-INF
> MANIFEST.MF
> application.xml
> ejb
> BatchAddition.jar
> ...
> eif-service_locator.jar
> ....
> </root>
>
> When I deploy my EAR and start JBoss 3.0.6, I receive the following
> warnings, which eventually lead to stack traces caused by
> NoClassDefFoundError:
>
> 2003-01-29 15:14:29,091 WARN [org.jboss.deployment.MainDeployer] The
> manifest entry in
>
file:/C:/tools/jboss-3.0.6/server/apogent_dss/tmp/deploy/server/apogent_dss/
>
deploy/dss_ras_production.ear/26.dss_ras_production.ear-contents/ejb/BatchAd
> dition.jar references URL
>
file:/C:/tools/jboss-3.0.6/server/apogent_dss/tmp/deploy/server/apogent_dss/
>
deploy/dss_ras_production.ear/26.dss_ras_production.ear-contents/ejb/eif-ser
> vice_locator.jar which could not be opened, entry ignored
>
> It is true that my library JARs, such as eif-service_locator.jar above,
are
> not present in the temporary folder indicated above. In fact, the only
file
> ever present there is BatchAddition.jar. This EAR structure works in
JBoss
> 2.4.10, and the FAQs for JBoss 3 indicate that it should work. The
> application.xml contains all EJBs, and each JAR in the ejb folder of the
EAR
> has a manifest classpath entry for the libraries at the root of the EAR.
>
> I would greatly appreciate any help that you can offer. Also, please
point
> me to any advice there may be for migrating from 2.4.x to 3.0.x.
>
> Many thanks for your time,
> Craig
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
