On the other hand, I've never had any success getting output from Log4j, and I pretty much hate the whole thing. My preferred solution is a simple class that handles log requests. I don't see much need for anything more complicated than that.
-Mike On 21 Aug 2002 at 15:49, Wolfram Rittmeyer wrote: > log4j is already in the lib-path (though not the actual one - you still have > to use Category instead of Logger for instance). It works perfectly well in > conjunction with JMeter. And log4j is already in use - though not in > general. If you swith to DEFAULT (in bin/log4j.conf) you already get a whole > lot of logging. > > Anyway: I agree with you that this should be the normal way of dealing with > any output that has to be generated (e.g. TableVisualizer/TableDataModel > produces a lot of System.out-messages). Maybe we could even migrate to the > commons-logging-library since this would allow JDK1.4 users to utilize > JDK-logging while those preferring log4j or using older JDKs can do so as > well. > > And finally: Shame on me! I still used "System.out" in DurationAssertionGui. > I'm going to correct that ;-) > > Greetings, > > Wolfram > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
