Although it may not be needed for the default sars,
we do need the ability to specify a classpath in the event
that the service refers to an external set of jars as is the
case with the tomcat4 service.

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "David Jencks" <[EMAIL PROTECTED]>
To: "Hiram Chirino" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, March 01, 2002 11:39 AM
Subject: Re: [JBoss-dev] Property access in *service.xml and relative paths


> On 2002.03.01 14:10:07 -0500 Hiram Chirino wrote:
> > How does the server know where the jars are if the <classpath../> is not
> > there.  Does it just load up all the lib/* jars??
>
> yes
>
> david jencks
> >
> > Regards,
> > Hiram
> >
> >
> > >From: David Jencks <[EMAIL PROTECTED]>
> > >To: Hiram Chirino <[EMAIL PROTECTED]>
> > >CC: [EMAIL PROTECTED], [EMAIL PROTECTED]
> > >Subject: Re: [JBoss-dev] Property access in *service.xml and relative
> > paths
> > >Date: Fri, 1 Mar 2002 10:39:55 -0500
> > >
> > >Are you sure you need the <classpath .../> element at all? Unless you
> > are
> > >loading from an http: url you should be fine by removing this element
> > >entirely.  I guess I better go through everything and do this... I
> > already
> > >got a lot of messages from them being in the db config examples.
> > >
> > >david jencks



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to