It's exceptions all the way down, man ;-) The issue is that FATAL, as defined in the Log4J manual, is something that should never happen, ie the process should stop...
Scott > -----Original Message----- > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 30, 2002 2:30 PM > To: Jakarta Commons Developers List > Subject: RE: [Logging] [VOTE-REDUX] Commons Logging 1.0 Release > > > > > On Wed, 30 Jan 2002, Scott Sanders wrote: > > > Date: Wed, 30 Jan 2002 14:13:40 -0800 > > From: Scott Sanders <[EMAIL PROTECTED]> > > Reply-To: Jakarta Commons Developers List > > <[EMAIL PROTECTED]> > > To: Jakarta Commons Developers List <[EMAIL PROTECTED]> > > Subject: RE: [Logging] [VOTE-REDUX] Commons Logging 1.0 Release > > > > I personally believe that a fatal 'log' should just be an > Exception, > > but I could be wrong :) > > > > What should the poor code that receives that exception do to > let somebody know that something really bad happened? > > > Scott > > Craig > > > -- > To unsubscribe, e-mail: > <mailto:commons-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
