cvs commit: jakarta-jmeter/src/core/org/apache/jmeter/threads JMeterThread.java

2003-05-30 Thread mstover1
mstover12003/05/29 06:33:57 Modified:src/components/org/apache/jmeter/modifiers/gui UserParametersGui.java src/core/org/apache/jmeter/gui AbstractJMeterGuiComponent.java GuiPackage.java

RE: Logging suggestions

2003-05-30 Thread BAZLEY, Sebastian
Given that changing the logging category would mean changes to all source files that use logs, it seems to me that it might be worth taking the opportunity to start using the Commons Logging wrapper interface. This offers more flexibility, e.g. choice of logging package at run-time. But it does

RE: Logging suggestions

2003-05-30 Thread mstover1
There is a LoggingManager class in the jorphan code that I use that's really simple, and it has a public method you can call to change the priority for any category at runtime. It just needs to be made static and you have exactly what you want. Furthermore, all classes currently have some

DO NOT REPLY [Bug 20181] - Webservice that require text/xml encoding doesn't work correctly

2003-05-30 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20181. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 20181] - Webservice that require text/xml encoding doesn't work correctly

2003-05-30 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20181. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

DO NOT REPLY [Bug 20181] - Webservice that require text/xml encoding doesn't work correctly

2003-05-30 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20181. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

RE: Logging suggestions

2003-05-30 Thread BAZLEY, Sebastian
Yes, thanks, agreed - that would simplify/rationalise the logging using Avalon logkit. But it would not allow the use of LOG4J or Java 1.4 logging without edit/recompile, AFAIK. For most source files, the changes to convert to Commons Logging would be very similar to those needed to tidy up the

RE: Logging suggestions

2003-05-30 Thread mstover1
On 30 May 2003 at 11:41, BAZLEY, Sebastian wrote: Yes, thanks, agreed - that would simplify/rationalise the logging using Avalon logkit. But it would not allow the use of LOG4J or Java 1.4 logging without edit/recompile, AFAIK. For most source files, the changes to convert to Commons

Re: Logging suggestions

2003-05-30 Thread Jeremy Arnold
Hello, I don't have a strong opinion about this, although personally I like Log4J. However, my general opinion is that using Commons Logging is great for library code, since this makes it possible to use the same logging setup for several libraries used by one application. But when

Re: Logging suggestions

2003-05-30 Thread mstover1
On 30 May 2003 at 14:15, Jeremy Arnold wrote: Hello, [snip] For making changes to the call to getLoggerFor( ) for all of the classes, it might be easier for one of the committers to do this directly, rather than dealing with patches. That's very true. -Mike BAZLEY,