Paulo Gaspar wrote:
Well, we are deprecating that logger as it puts us (Velocity
devs) into the
position to have to support every possible app usage of log4j.
The replacement just takes a category, so you can configure things in your
app as you want (not hope that we provided the
: [Logging] [VOTE-REDUX] Commons Logging 1.0 Release
On Wed, 30 Jan 2002, Craig R. McClanahan wrote:
(3) Change the message argument type from Object to String
A big -1.
Object in the interface will allow loggers to provide 'render'-like
capability. This would allow passing things
On Fri, 1 Feb 2002, Paulo Gaspar wrote:
Now, since you are also a security freak (like Peter Donald) I
have a (Devil's Advocate) question:
- What is the way to avoid that a hostile logger accesses the
objects that are passed to it?
I'll send a longer email with comments on the logger -
Out of the discussions yesterday, the proposal to release
commons-logging 1.0 received a sufficient number of +1 votes to pass.
Howeer, three issues were raised that should be settled beforehand, in
order to provide future users of this package with a stable API. I'd like
to review them
: [Logging] [VOTE-REDUX] Commons Logging 1.0 Release
SNIP /
(1) Attribution
As was pointed out, the developers of the Avalon framework, and the
logging abstractions and implementations they have developed, had an
influence on the development of the Commons Logging API. In particular,
my
On Wed, Jan 30, 2002 at 08:40:27AM -0800, Craig R. McClanahan wrote:
Out of the discussions yesterday, the proposal to release
commons-logging 1.0 received a sufficient number of +1 votes to pass.
Howeer, three issues were raised that should be settled beforehand, in
order to provide future
] Commons Logging 1.0 Release
On Wed, Jan 30, 2002 at 08:40:27AM -0800, Craig R. McClanahan wrote:
Out of the discussions yesterday, the proposal to release
commons-logging 1.0 received a sufficient number of +1
votes to pass.
Howeer, three issues were raised that should be settled
usefulness. Not to talk about the very cluttered API!
Have fun,
Paulo Gaspar
-Original Message-
From: Scott Sanders [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 30, 2002 8:17 PM
To: Jakarta Commons Developers List
Subject: Re: [Logging] [VOTE-REDUX] Commons Logging 1.0
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
-
From: Scott Sanders [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 30, 2002 11:14 PM
To: Jakarta Commons Developers List
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
] [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
11 matches
Mail list logo