I just modified the old JAWS JDBCCommand stuff to log4j today. I wish I did
not have to spend the time to do it either. If you find something that is
not log4j and you can make it log4j (with out much work) then do it. I can
not see any reason not to. The old logging system does not provide enough
direct information, lets get rid of it. For example JDBCCommand exceptions
show up as AutoDeployer log messages, which is crap in my opinion.
If I did not have at least a hundred other things todo, I would sit down and
change everything to log4j...
Scott, what are your toughts on dropping the old Log and Logger classes and
replacing them with log4j, perhaps re-writing Logger to be the JBossCategory
and using it *everywhere* instead of Category, JBossCategory or any of the
current Log or Logger bits?
--jason
On Fri, 10 Aug 2001, danch wrote:
> Vincent Harcq wrote:
>
> > Hi,
> > I modify JDBCCommand & co to use log4j for debugging.
> >
> > Should I commit that ?
>
> Please. was this in the mainline, or the 2.4 branch? If mainline, the
> old JAWS stuff or the new ejb2.0 CMP stuff?
>
>
> >
> > I also get rid of debug option of standardjaws.xml to use log4j declaration
> > instead.
> > It permits better control on which class to debug (find,update,...)
>
> Can you repeat that and use smaller words for me? I don't understand
> what you've changed here.
>
>
> >
> > Should I commit that ?
> > My concern is regarding performance changes it will cause.
> >
> > Regards.
> > Vincent.
>
> thanks,
> danch
>
>
>
>
> _______________________________________________
> 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
