Return-Path: 
 <tomcat-dev-return-35040-apmail-jakarta-tomcat-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org
Received: (qmail 34844 invoked from network); 3 Oct 2003 13:54:50 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 3 Oct 2003 13:54:50 -0000
Received: (qmail 60335 invoked by uid 500); 3 Oct 2003 13:54:39 -0000
Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org
Received: (qmail 60218 invoked by uid 500); 3 Oct 2003 13:54:38 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-dev-help@jakarta.apache.org>
List-Post: <mailto:tomcat-dev@jakarta.apache.org>
List-Id: "Tomcat Developers List" <tomcat-dev.jakarta.apache.org>
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 60205 invoked from network); 3 Oct 2003 13:54:38 -0000
Received: from unknown (HELO crusher.cincom.com) (198.8.67.11)
  by daedalus.apache.org with SMTP; 3 Oct 2003 13:54:38 -0000
Received: by mailer.cincom.com with Internet Mail Service (5.5.2656.59)
	id <TXFAXQ85>; Fri, 3 Oct 2003 10:01:21 -0400
Message-ID: <399E1F52E73BD41194A800D0B74A08AB03400410@skipper.cincom.com>
From: "Cox, Charlie" <ccox@cincom.com>
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: FW: [next] What's next ?
Date: Fri, 3 Oct 2003 09:48:09 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

for some reason this didn't get through to the list yesterday. If you get
this twice, I apologize

Charlie

-----Original Message-----
From: Cox, Charlie 
Sent: Thursday, October 02, 2003 2:12 PM
To: 'Tomcat Developers List'
Subject: RE: [next] What's next ?




> -----Original Message-----
> From: Remy Maucherat [mailto:remm@apache.org]
> Sent: Thursday, October 02, 2003 12:06 PM
> To: Tomcat Developers List
> Subject: Re: [next] What's next ?
> 
> 
> Shapira, Yoav wrote:
> 
> > Howdy,
> > 
> >>I think this kind of classloading structure can be 
> configured in TC 5
> >>using the catalina.properties.
> > 
> > If it can be achieved via configuration, I'm happy ;)  How can it be
> > done?
> 
> You can set empty contents to the repositories list in 
> catalina.properties, and then move whatever is required to 
> common/endorsed. The CL ierarchy will still exist (but they won't 
> contain anything).
> 

Will I be able to drop my own libraries in /common/endorsed to be used as
the /common/lib is today? per the other thread, native libraries will not
work in /WEB-INF/lib, so if I can put whatever I need into /common/endorsed,
then that would be ok. But I thought everything in the endorsed dir would be
treated as 'endorsed' libraries, or would I be able to configure that?

Maybe I don't understand enough about the endorsed libraries, if I put
something into /common/endorsed, that doesn't override an existing library,
is it just loaded as normal?

am I asking too many questions? :)

Charlie

> >>Is that useful ? I don't really see how. (ex: if you have 
> no loader for
> >>a webapp, it won't work) I think you should elaborate more.
> > 
> > I suggested that one in order to simply supporting users.  The less
> > stuff that happens behind the scenes as far as configuration, the
> > better.  It should all be visible, so that on the user 
> mailing list we
> > can say "this happens because line XXX of server.xml you have this
> > string."  Contrast with "as part of tomcat's default context
> > initialization, the property gets assigned this default 
> value, which you
> > can override by adding this element to server.xml, see 
> config reference
> > here."  The more users can see by themselves by inspecting 
> server.xml,
> > the better IMHO.
> 
> Possibly :)
> It's a bit hard to answer. The more XML is needed, the more 
> intimidating 
> it looks.
> 
> Remy
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org