- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 08, 2002 9:30 PM
Subject: Re: [JBoss-dev] Design: Plans to decouple JBoss from log4j
The major issue with Log4j that I have is size... it is huge. Commons is
very small
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Design: Plans to decouple JBoss from log4j
It is too bad commons logging does not provide abstractions
for a ContextStack or ContextMap similar to Log4j's NDC and
MDC. These are valuable constructs.
Do you know anyone on the commons logging team
]
Subject: Re: [JBoss-dev] Design: Plans to decouple JBoss from log4j
The major issue with Log4j that I have is size... it is huge. Commons is
very small. If Log4j has a 20k footprint (or smaller) for client usage an
dprovided a simple method to disable logging, then I would see no need
PROTECTED]] On Behalf Of James
Higginbotham
Sent: Friday, October 04, 2002 6:41 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Design: Plans to decouple JBoss from log4j
Do you know how you switch the LogFactory impl? I am
guessing there is a
system property, but I did not see anything
-Original Message-
From: [EMAIL PROTECTED] [mailto:jboss-
[EMAIL PROTECTED]] On Behalf Of James
Higginbotham
Sent: Friday, October 04, 2002 6:41 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Design: Plans to decouple JBoss from log4j
Do you know how you switch
: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 08, 2002 9:30 PM
Subject: Re: [JBoss-dev] Design: Plans to decouple JBoss from log4j
The major issue with Log4j that I have is size... it is huge. Commons is
very small. If Log4j has a 20k footprint (or smaller
I just looked over the commons logging api and it closly resembles
org.jboss.logging.Logger. The only major differences are that Logger is a
class and is serializable (the log4j commons log impl does not) not a big
deal, as we can write a subclass of the log4j log factory to produce
. oktober 2002 11:48
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Design: Plans to decouple JBoss from log4j
I just looked over the commons logging api and it closly resembles
org.jboss.logging.Logger. The only major differences are that Logger is
a
class and is serializable (the log4j commons log
Well, we happen to be one of the companies who would like JBoss to have
support for the logging system of what you call the JDK 1.4 crap API.
Ick *spit* Some like pain, some prefer pleasure ;)
But why is there no support for using the standard java.util.logging
mechanism with JBoss?
No
Do you know how you switch the LogFactory impl? I am
guessing there is a
system property, but I did not see anything obvious by looking at the
javadocs.
I've been using commons logging for a few months now - not bad at all..
You drive the impl from a properties file called
Title: Message
randahl,
I am
swimming back up this thread as it seems it has kicked up a fuss.
.
dude,
the bottom line is very simple. If you really care, you put your time on
the line, or you pay us to do it (we do a lot of work under contract for
customers on this list). I do believe
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of marc fleury
Sent: 4. oktober 2002 15:43
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] Design:
Plans to decouple JBoss from log4j
randahl,
I am
swimming back up this thread as it seems
Title: Message
| There is no
reason telling me the basics of the business, Morpheus -
|I might very
well swallow that famous addictive red pill you keep on pushing. It would
suit
I am indeed morpheus, and I am still looking for the
one. You kids keep on taking those pills, something tells
13 matches
Mail list logo
