I'm going ahead with JBossCategory, and removing setPrintWriter type
methods from code we control.
david
btw, what happened to running with the jca adapters? did it start working
or did you give up or find a fix? I'm also wondering if your machines are
multiprocessor. The race condition I found failed on my uniprocessor
machine, I very much wonder if we will find more on multiprocessor.
On 2001.08.17 15:30:05 -0400 Jason Dillon wrote:
> > You've replaced way more logging code than I have, I'll be happy to do
> it
> > especially if you can give me a model to copy, otherwise if you want to
> > that's fine too.
>
> No, be my honored guest!
>
> > There is no doubt about the need to replace logging in the actual jboss
> > framework components with log4j also, I guess I should have done it
> earlier
> > this week. Again - you or me?
>
> Again, I would replace (and have done so) all Log and Logger bits with
> Category or JBossCategory as long as it was trivial to do so. There are
> still places where Log.setLog() is used, which I think we need to get rid
> of, but I want to wait for the JBossCategory -> Logger stuff which Scott
> has
> mentioned before I even think about that... unless I can not get around
> it.
>
> I suggest that you, and others do the same.
>
> --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
