After some trial-and-error, I found <classpath ... /> entry in the .sar's jboss-service.xml starts at the deployment directory, instead of the ear. When I use a manifest for the .sar, which references the common libraries in the .ear, it works just fine... Thanks Wonne
-----Original Message-----
From: Scott M Stark [mailto:[EMAIL PROTECTED]
Sent: Wed 3/12/2003 3:07
To: [EMAIL PROTECTED]
Cc:
Subject: Re: [JBoss-user] Scoped classloading - .sar
There is no reason why the sar cannot use the common jars in
the ear. Submit a bug report with an example of the problem you see.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "Keysers, Wonne" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 10, 2003 11:45 AM
Subject: [JBoss-user] Scoped classloading - .sar
> Hi,
>
> Our webapp.war, ejbs.jar and services.sar are all in a application.ear,
> with scoped classloading enabled.
>
> What's the best way to make one or more libraries available for all
> these packages?
>
> It seems that the .war and .jar are able to use (client-)libraries from
> the .ear,
> but .sar files require them either to be in the serverconfig/lib
> directory or in the .sar
> itself?
>
> I wasn't able to find the answer in the classloading doc at
> sourceforge...
>
> Could someone provide some more information?
> Thanks
> Wonne Keysers
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
<<winmail.dat>>
