cvs commit: jakarta-log4j-sandbox/src/java/org/apache/log4j/servlet ConfigurationServlet.java

mwomack 2003/02/19 23:45:36 Modified:src/java/org/apache/log4j/servlet ConfigurationServlet.java Log: Jalopy-ized and checkstyle-d version. Revision ChangesPath 1.2 +260 -234 jakarta-log4j-sandbox/src/java/org/apache/log4j/servlet/ConfigurationServlet.java In

cvs commit: jakarta-log4j-sandbox/src/java/org/apache/log4j/servlet CookieMDCFilter.java

mwomack 2003/02/19 23:35:38 Modified:src/java/org/apache/log4j/servlet CookieMDCFilter.java Log: Jalopy-ized and checkstyle-d version. Revision ChangesPath 1.2 +94 -77 jakarta-log4j-sandbox/src/java/org/apache/log4j/servlet/CookieMDCFilter.java Index: Cooki

cvs commit: jakarta-log4j-sandbox build.xml

mwomack 2003/02/19 23:32:51 Modified:.build.xml Log: Checked in property settings for checkstyle task. Allow "public" modifier in interfaces. Allow protected members in classes. Revision ChangesPath 1.5 +2 -7 jakarta-log4j-sandbox/build.xml Inde

cvs commit: jakarta-log4j/src/java/org/apache/log4j/plugins Receiver.java PluginSkeleton.java PluginRegistry.java Plugin.java

mwomack 2003/02/19 23:18:32 Modified:src/java/org/apache/log4j/plugins Receiver.java PluginSkeleton.java PluginRegistry.java Plugin.java Log: Jalopy-ized and checkstyle-d versions of the plugin files. Revision ChangesPath 1.3 +24 -23jakar

cvs commit: jakarta-log4j build.xml

mwomack 2003/02/19 23:12:53 Modified:.build.xml Log: Checked in property settings for checkstyle task. Allow "public" modifier in interfaces. Allow protected members in classes. Revision ChangesPath 1.52 +2 -7 jakarta-log4j/build.xml Index: build

DO NOT REPLY [Bug 17227] New: - Links for sample XMLs are inaccurate

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: Chainsaw and multiple files

Hi, To answer your questions: 1. Yes, this is desired behaviour. The intention is to allow different different logs to be analysed at the same time. Very useful when trying to analyse a distributed application. 2. I would prefer to set them globally. I would rather wait to see if the re

Chainsaw and multiple files

All, I noticed that when you load multiple files with chainsaw that the effect is cumulative, i.e., logging events from all the files are simultaneously loaded. I am in the process of creating a recent files menu and I was going to save the state of the filters for each file. However, given t

Re: JDBCAppender proposal

Mark Womack wrote: Mike, I second Ceki on this. It is still in 1.2.8, and it looks like it is going to get some major attention in v1.3. So, I wouldn't worry too much. But it does sound like it's features/method signature will be changing in v1.3 (depending on the extent of the re-write), but

Re: JDBCAppender proposal

Just for interest sake, are you going to record a row in the table for each log statement, or a row for each log file (as it were)? Here at work we started doing a row per log statement, but our code produces a prodigious number of log statments, so that each run of the application was filling up

RE: JDBCAppender proposal

Sounds good. I have no problem if details change, I was just concerned if the entire support for JDBC might have been dropped. Thanks a lot for your responses. -Original Message- From: Mark Womack [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 1:07 PM To: 'Log4J Develope

RE: JDBCAppender proposal

Mike, I second Ceki on this. It is still in 1.2.8, and it looks like it is going to get some major attention in v1.3. So, I wouldn't worry too much. But it does sound like it's features/method signature will be changing in v1.3 (depending on the extent of the re-write), but you will get plenty

RE: JDBCAppender proposal

Mike, There is no need to worry. JDBCAppender will have a replacement in version 1.3. Moreover, it was not removed in 1.2.8. At 10:01 19.02.2003 -0500, you wrote: I just wanted to express concern about ripping it out (even if it's a temporary move) without a replacement. I've got existing doc

Release of log4j version 1.2.8

Log4j developers are proud to announce the immediate availability of log4j version 1.2.8, a purely maintenance release. In particular, it fixes a parsing problem of log4j configuration files written in XML observed with certain versions of Xerces. You can download log4j version 1.2.8 at

RE: JDBCAppender proposal

I just wanted to express concern about ripping it out (even if it's a temporary move) without a replacement. I've got existing documentation at my company telling people how to use the JDBC Appender, and there are plans to use it in production. I have to think this situation is common. Removin

Re: JDBCAppender proposal

Unless someone does it before, I intend to rewrite the JDBCAppender completely. Removing the existing JDBCAppender is my preferred choice. At 22:11 18.02.2003 -0800, you wrote: I propose that we place the current version of o.a.log4j.jdbc.JDBCAppender.java into the log4j-sandbox (I don't know if

Re: cvs commit: jakarta-log4j/src/java/org/apache/log4j/xml DOMConfigurator.java

Forgot to comment the commit. The relevant part is included below: At 14:24 19.02.2003 +, you wrote: docBuilder.setEntityResolver(new Log4jEntityResolver()); + // we change the system ID to a valid URI so that Crimson won't + // complain. Indeed, "log4j.dtd" alone is not a vali

cvs commit: jakarta-log4j/src/java/org/apache/log4j/xml DOMConfigurator.java

ceki2003/02/19 06:29:40 Modified:src/java/org/apache/log4j/xml Tag: v1_2-branch DOMConfigurator.java Log: Forgot to include comments in the previous commit. Artifically changing the system id from "log4j.dtd" to "dummy://log4j.dtd" and setting an en

RE: JDBCAppender proposal

Mark, Does this mean that when someone downloads Log4j 1.2.8, the JDBC Appender wouldn't be included? Mike -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 19, 2003 1:12 AM To: Log4J Developers List Subject: JDBCAppender proposal I pro

cvs commit: jakarta-log4j/src/java/org/apache/log4j/xml DOMConfigurator.java

ceki2003/02/19 06:24:06 Modified:src/java/org/apache/log4j/jdbc Tag: v1_2-branch JDBCAppender.java src/java/org/apache/log4j/xml Tag: v1_2-branch DOMConfigurator.java Log: Revision ChangesPath No

DO NOT REPLY [Bug 17201] New: - DailyRollingFileAppender and multi-instance

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-log4j/tests/src/java/org/apache/log4j/xml XMLLayoutTestCase.java

ceki2003/02/19 05:37:36 Modified:src/xdocs/stylesheets Tag: v1_2-branch project.xml tests/src/java/org/apache/log4j/xml Tag: v1_2-branch XMLLayoutTestCase.java Log: Minor changes to bring the 1.2 in sync with main brach Revision Change