If there is any logging api other than System.out, then its log4j as
far as I'm concerned. We can provide a null config if they want
to disregard any JBoss generated client side logging.
----- Original Message -----
From: "Jason Dillon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 09, 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 enable with a system property), but either way make use
of
> the same logging api calls. I do not think it is reasonable to assume
that
> all clients will have Log4j configured.
>
> --jason
>
>
> On Tue, 10 Jul 2001, Hiram Chirino wrote:
> >
> > Yes, but what about on the client side??? Can my client side code also
use
> > log4j??
> >
> > Regards,
> > Hiram
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
