tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Larry Isaacs <Larry.Isa...@sas.com>
Subject RE: Outstanding bugs before 3.2 final?
Date Fri, 22 Sep 2000 01:57:41 GMT
The plumbing problem didn't turn out to be a big as I thought it would.

I'll implement this tonight.  I don't know why my mind didn't want to
accept that it was this simple.

Thanks.

Larry 

-----Original Message-----
From: Alex Chaffee
To: tomcat-dev@jakarta.apache.org
Sent: 9/21/00 8:09 PM
Subject: Re: Outstanding bugs before 3.2 final?

On Thu, Sep 21, 2000 at 05:11:35PM -0700, cmanolache@yahoo.com wrote:
> 
> We can just add a get/setStackTraces() to ContextManager, you don't
need
> any other "configuration changes" ( plus if( cm.getStackTraces())
before 
> printing that traces ). 
> 

Let's name it setShowStackTraces (to distinguish from a potential
future setLogStackTraces determining if full stack traces show up in
log files too).

Then the setting in server.xml would be

 <ContextManager debug="0" workDir="work" showStackTraces="false">

if you want to disable it.
  
God bless reflection!

 - A


-- 
Alex Chaffee                       mailto:alex@jguru.com
jGuru - Java News and FAQs         http://www.jguru.com/alex/
Creator of Gamelan                 http://www.gamelan.com/
Founder of Purple Technology       http://www.purpletech.com/
Curator of Stinky Art Collective   http://www.stinky.com/

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

Mime
View raw message