I am not so sure that is a safe assumption. For example, the testsuite does
not currently setup any logging on the clients. So if JBossMQ used Log4j in
its client code, the current testsuite will produce a lot of garbage
messages about needing some configuration.
There is also the issue of serialization. Category is not serializable, so
special care needs to be taken for those classes which need to log, but also
need to be serializable. It is really too bad that they did not do this as
to avoid the private void readObject(...) overrides that are required to
make this work.
I have a logging facade which provides all of this niceness and adapts to
Log4j (and a custom nexus based system that it originally was based on). I
was going to suggest that we make use of it as soon as I was finished with
the current refactoring. It provides some convience methods to deal with
parameter concatination, logging primitives and handling serialization and
such.
I wanted to fixed up the Log4j integration, perhaps with a simple
autoconfig, that would setup a PrintLogger or NullLogger where Log4j was not
available on the client side.
Either way, the JBossMQ code should use a more robust logging system. I was
going to blanket replace all of the logging in JBossMQ with Log4j until I
started running into serialization problems.
--jason
On Tue, 10 Jul 2001, Hiram Chirino wrote:
>
> 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 and Log4j
> >Date: Thu, 5 Jul 2001 23:05:01 -0700
> >
> >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
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>
> _______________________________________________
> 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
