Why not use the logging mbean? That would abstract out the logging
facility, so that you can use the Log4J logging mbean or some other logging
facility in the future. Of course, maybe that's exactly what you're asking
for.
I agree that stdout is not acceptable over the long run. Go 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 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 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 mailing list
> |[EMAIL PROTECTED]
> |http://lists.sourceforge.net/lists/listinfo/jboss-development
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
