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: Thursday, July 05, 2001 9:09 PM
Subject: [JBoss-dev] JBossMQ and Log4j
> Is there any reason why JBossMQ does not use the Log4j api for logging? I
> am having a hard time tracking down this EOFException problem due to
either
> the lack of messages or a complete overload of them. If Log4j was used
> here (with category names set to classnames), I could turn down the
noise...
> or at least limit it.
>
> 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?
>
> --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
