away.
Plus, since marcf is going to make deploying JMX services so easy, doing
things like adding queues and topics will be a snap!
Regards,
Hiram
From: Jason Dillon [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] JBossMQ and Log4j
Date: Mon, 9 Jul
PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] JBossMQ and Log4j
Date: Mon, 9 Jul 2001 23:16:44 -0700
Log4j will be configured as a service of JBoss.
- Original Message -
From: Hiram Chirino [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent
Before you go crazy on that log system clean up... I'm working on a major
re-org of the jbossmq module. It's so major that everything is broken right
now on my development box :) I'm making all subsytems in jbossmq a JMX
service. This will be good since jbossmq.xml will then be able to go
, 2001 11:48 PM
Subject: Re: [JBoss-dev] JBossMQ and Log4j
I would say that in the short term that it would be better to have the
client code using Log4j, so we can better debug things. In the long term
we
need to have a way to let the client side logging either automatically
disable (perhaps
Ah... I did not know that! I've allready moved most of the server over to
log4j. Can I just assume that log4j will be confiurged for me by the
client??
Regards,
Hiram
From: Scott M Stark [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] JBossMQ
Log4j will be configured as a service of JBoss.
- Original Message -
From: Hiram Chirino [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, July 09, 2001 10:34 PM
Subject: Re: [JBoss-dev] JBossMQ and Log4j
Ah... I did not know that! I've allready moved most of the server over
Yes, but what about on the client side??? Can my client side code also use
log4j??
Regards,
Hiram
From: Scott M Stark [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] JBossMQ and Log4j
Date: Mon, 9 Jul 2001 23:16:44 -0700
Log4j will be configured
Sorry, let me rephrase... Can I assume the a client VM will be on it's own
to figure out how to configure lo4j??
Regards,
HIram
From: Scott M Stark [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] JBossMQ and Log4j
Date: Mon, 9 Jul 2001 23:16:44
that log4j will be confiurged for me by the
client??
Regards,
Hiram
From: Scott M Stark [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] JBossMQ and Log4j
Date: Thu, 5 Jul 2001 23:05:01 -0700
The only reason log4j is not used is because no one
for it!
-dan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
Dillon
Sent: Friday, July 06, 2001 5:38 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] JBossMQ and Log4j
So are there any objections to changing all JBossMQ logging to Log4j? If
not then I am
|The only reason that I can think not to use Log4j is that we then force
|clients to have Log4j and configure it. Is that such a bad thing?
The only reason I can think of is that no one has coded it ;)
marcf
|
|--jason
|
|
|___
|Jboss-development
So are there any objections to changing all JBossMQ logging to Log4j? If
not then I am gonna do it, these System.out's are driving me crazy
(especially when mixed in with Log4j output).
--jason
On Fri, 6 Jul 2001, marc fleury wrote:
|The only reason that I can think not to use Log4j is that
The only reason log4j is not used is because no one has done it. Clients are
already required to use log4j if they want integration with the JBoss
logging
facility as of 2.4 so that is not a reason.
- Original Message -
From: Jason Dillon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent:
13 matches
Mail list logo
