commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Downey <steve.dow...@netfolio.com>
Subject RE: [VOTE] Logging 1.0 Release (again)
Date Wed, 20 Feb 2002 05:00:39 GMT


> -----Original Message-----
> From: Craig R. McClanahan [mailto:craigmcc@apache.org]
> Sent: Tuesday, February 19, 2002 8:27 PM
> To: Jakarta Commons Developers List
> Subject: RE: [VOTE] Logging 1.0 Release (again)
> 
> 
> 
> 
> On Tue, 19 Feb 2002, Steve Downey wrote:
> 
> > Date: Tue, 19 Feb 2002 20:07:35 -0500
> > From: Steve Downey <steve.downey@netfolio.com>
> > Reply-To: Jakarta Commons Developers List 
> <commons-dev@jakarta.apache.org>
> > To: 'Jakarta Commons Developers List' 
> <commons-dev@jakarta.apache.org>
> > Subject: RE: [VOTE] Logging 1.0 Release (again)
> >
> > -1 as long as LogSource uses catch(Throwable){}
> >
> > It is far too risky in server side code to catch all thrown 
> exceptions and
> > errors.
> >
> > SWALLOWING them to boot is unforgivable.
> >
> 
> Steve,
> 
> One thing to note is that LogSource is deprecated, and only there for
> backwards compatibility for modules that depended on the prerelease
> version.
> 
> Craig
> 
> 

Even a deprecated loaded gun is dangerous. And nothing seems to be quite so
permanant as something documented as deprecated. The argument that some
programs may depend on the deprecated API does not seem to loose power over
time.  

I'm not suggesting removing LogSource immediately, merely fixing it so that
it's not a ticking bomb.

Then httpclient can replace their implementation of logging that has the
same bug.


Mime
View raw message