Sure looks simple doesn't it?
Manifest-Version: 1.0
Class-Path: library/mylib.jar library/myotherlib.jar
I tried this on weblogic 6.0 and 6.1 long ago and it did not work. I tried
it again this afternoon using a variety of simple configurations in 6.1 SP2
and it failed. I opened a case with BEA support so we will see what the deal
is from their perspective. When evaluating JBoss 3.2 this same strategy was
tried and it failed. A couple of people posted that it worked fine under
3.0.4 but perhaps they had those jars in the path in addition to the
manifest file. Followed the same process you did; made sure there was a
blank line under the Class-Path line an so on. Mine happens to be the
MANIFEST.MF of a war file that is part of my EAR but same concept. It's easy
enough to work around with the library or system class path or just jarring
up everything multiple times. Perhaps that is why this problem is being
brushed off. AFAIAC it simply does not work.
Remember my spiel about the <java> module? Add an entry in application.xml
for each loose jar and it will all magically work. Sad thing is that fails
on weblogic. Argggg!
<!-- Causes foo.jar to magically appears before all the jars 'n wars in this
ear -->
<module>
<java> foo.jar </java>
</module>
I wish they would make that a standard and ditch the non-functional, one-off
odd-ball Class-Path thing. I am still leaving the door open that this
failure is actually a dumb mistake on my part -- basing that on experience:)
I think your seeing a situation where the behavior has simply changed from
2.X to 3.X.
----- Original Message -----
From: "Demyanovich, Craig - Apogent" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 31, 2003 8:43 AM
Subject: RE: [JBoss-user] EAR works in 2.4.10 but not in 3.0.6
> Rod,
>
> Attached is my application.xml.
>
> The floating JAR, eif-service_locator.jar, does not have a module type;
it's
> a JAR that contains dependencies for many of the EJBs. Check this
reference
> (http://www.jboss.org/faq.jsp#FAQ-BEANDEV-NORMALJARS) for how I have my
EAR
> structured. All EJBs listed in application.xml have a manifest file whose
> Class-Path entry lists eif-service_locator.jar and other "floating JARs"
(I
> like your terminology ;-)). Likewise, I would like to know what the
> expected or spec-compliant behavior is for support JARs.
>
> Again, thanks for your help,
> 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
