JDBCAppender proposal

I propose that we place the current version of o.a.log4j.jdbc.JDBCAppender.java into the log4j-sandbox (I don't know if we should remove it altogether from the v1.3 release?). In doing so, interested log4j developers need to step forward to begin the task of continuing its development. I know Kev

cvs commit: jakarta-log4j build.xml build.properties.sample sunCodingConvention.xml

mwomack 2003/02/18 21:51:47 Modified:.build.xml build.properties.sample Removed: .sunCodingConvention.xml Log: Moved sunCodingConvention.xml to src/jalopy/log4j-coding-convention.xml and updated build script accordingly. Updated log4j-coding-convention to cha

cvs commit: jakarta-log4j/src/jalopy log4j-coding-convention.xml

mwomack 2003/02/18 21:50:54 Added: src/jalopy log4j-coding-convention.xml Log: Moved sunCodingConvention.xml to src/jalopy/log4j-coding-convention.xml and updated build script accordingly. Updated log4j-coding-convention to changes suggested by Jake (brought over version from s

cvs commit: jakarta-log4j/src/jalopy - New directory

mwomack 2003/02/18 21:49:34 jakarta-log4j/src/jalopy - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: jakarta-log4j-sandbox/src/jalopy log4j-coding-convention.xml

mwomack 2003/02/18 21:43:17 Added: src/jalopy log4j-coding-convention.xml Log: Moved sunCodingConvention.xml to src/jalopy/log4j-coding-convention.xml and updated build script accordingly. Revision ChangesPath 1.1 jakarta-log4j-sandbox/src/jalopy/log4j

cvs commit: jakarta-log4j-sandbox build.xml build.properties.sample sunCodingConvention.xml

mwomack 2003/02/18 21:43:04 Modified:.build.xml build.properties.sample Removed: .sunCodingConvention.xml Log: Moved sunCodingConvention.xml to src/jalopy/log4j-coding-convention.xml and updated build script accordingly. Revision ChangesPath 1.4

cvs commit: jakarta-log4j-sandbox/src/jalopy - New directory

mwomack 2003/02/18 21:40:14 jakarta-log4j-sandbox/src/jalopy - New directory - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: Possible 1.2.8 release

#14827 fix is in place on 1.2 branch. > -Original Message- > From: Ceki Gülcü [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 18, 2003 10:24 AM > To: Log4J Developers List > Subject: RE: Possible 1.2.8 release > > > > Given that the existing JDBCAppender has other serious problems, I

cvs commit: jakarta-log4j/src/java/org/apache/log4j/jdbc JDBCAppender.java

mwomack 2003/02/18 21:21:42 Modified:src/java/org/apache/log4j/jdbc JDBCAppender.java Log: Fix for #14827. Revision ChangesPath 1.8 +6 -0 jakarta-log4j/src/java/org/apache/log4j/jdbc/JDBCAppender.java Index: JDBCAppender.java

cvs commit: jakarta-log4j/docs HISTORY

mwomack 2003/02/18 21:04:49 Modified:docs Tag: v1_2-branch HISTORY Log: Mention of fix for #14827. Revision ChangesPath No revision No revision 1.97.2.18 +5 -1 jakarta-log4j/docs/HISTORY Index: HISTORY ==

DO NOT REPLY [Bug 14827] - JDBCAppender removes list keeps growing

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/src/java/org/apache/log4j/jdbc JDBCAppender.java

mwomack 2003/02/18 20:55:57 Modified:src/java/org/apache/log4j/jdbc Tag: v1_2-branch JDBCAppender.java Log: Fix for #14827, memory leak related to the "removes" buffer. Revision ChangesPath No revision No

DO NOT REPLY [Bug 14827] - JDBCAppender removes list keeps growing

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

DO NOT REPLY [Bug 16998] - JDBCAppender leaks memory

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: Log4j.DTD update

If you like, you can update the DTD yourself and submit a patch... At 12:22 18.02.2003 -0800, you wrote: Thanks for the fix, Ceki. How do I request the DTD be updated to reflect the missing capabilities in LoggingEvent? I need support in the .dtd for the new properties and the MDC. Would this

RE: cvs commit: jakarta-log4j/src/java/org/apache/log4j/spi Loggi ngEvent.java

Yes, that's the logical next step. At 21:11 18.02.2003 +, you wrote: I would suggest adding support to the pattern layout to support the logging event properties. Syntax like: %P{name} Would be sufficient. Nicko > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTEC

EntityResolver code+DTD issues

Interestingly enough, the Log4jEntityResolver code as proposed in 1.2.8 (not yet released) does not work with the XML parser that ships in JDK 1.4 although it works fine with xerces. Trying to parse the following config file with DOMConfigurator and the JDK 1.4 XML parser will barf: ...

RE: Chainsaw improvement question - support for multiple sources

Hey Oliver, thanks for the info. I agree. I'll be happy to provide patches in stages. The features I listed first in my email are the ones I haven't started yet. I have written a UDPReceiver that accepts data via a UDPAppender defined with an XMLLayout pointing to a multicast address. The da

RE: Chainsaw improvement question - support for multiple sources

Scott, The changes you have/are making sound great. It would make sense if you could make the contributions in stages, rather than in one big hit. The advantage of stages are: - It allows for earlier feedback on code style and direction - The benefit of the changes made so far are able to be

RE: cvs commit: jakarta-log4j/src/java/org/apache/log4j/spi LoggingEvent.java

I would suggest adding support to the pattern layout to support the logging event properties. Syntax like: %P{name} Would be sufficient. Nicko > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: 18 February 2003 19:58 > To: [EMAIL PROTECTED] > Subject: cvs

Log4j.DTD update

Thanks for the fix, Ceki. How do I request the DTD be updated to reflect the missing capabilities in LoggingEvent? I need support in the .dtd for the new properties and the MDC. Would this require a new version of 1.3 as well? Thanks, Scott -Original Message- From: [EMAIL PROTECTED]

cvs commit: jakarta-log4j/src/java/org/apache/log4j/spi LoggingEvent.java

ceki2003/02/18 11:58:10 Modified:src/java/org/apache/log4j/spi LoggingEvent.java Log: Added a property map, similar to the one found in javax.jms.Message. The intention is to let appenders set properties and have layouts access them. Revision ChangesPath 1.35

AW: good EntityResolver code

Hi, what about something like that: import java.io.*; import java.net.*; import org.xml.sax.*; public class URLEntityResolver implements EntityResolver { public URLEntityResolver() { } public InputSource resolveEntity (String name, String uri) throws IOException, SAXExce

Re: Chainsaw improvement question - support for multiple sources

At 10:03 18.02.2003 -0800, Scott Deboy wrote: Is there some architectural changes to log4j in the pipe that will provide this functionality or make adding these identifiers easier? Yes, indeed. In 1.3 LoggingEvent will contain an extra field called "properties" containing a map of keys and valu

RE: cvs commit: jakarta-log4j/tests/witness xmlLayout.null

The change is o.a.l.helpers.Transform.java not XMLLayout: http://marc.theaimsgroup.com/?l=log4j-dev&m=104558701929938&w=2 At 10:43 18.02.2003 -0800, you wrote: I see the changes for the test case, but I don't see a check in for the 11570 fix. ? -Mark > -Original Message- > From: [EMA

Re[2]: Indentation!!!

Hello Mark, In addition to making mods to build.xml, selector and servlet initializers, I also took the liberty of adding the mods to the sunCodingConvention.xml that we agreed to. So, make sure it isn't already there before you check anything in. Jake Tuesday, February 18, 2003, 12:25:47 PM, y

RE: cvs commit: jakarta-log4j/tests/witness xmlLayout.null

I see the changes for the test case, but I don't see a check in for the 11570 fix. ? -Mark > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 18, 2003 8:39 AM > To: [EMAIL PROTECTED] > Subject: cvs commit: jakarta-log4j/tests/witness xmlLa

RE: Configuration GUI & logging.apache.org

Nuts. >From the feedback this morning it sounds like this will be an architectural issue for the different log4x groups to sort out together. Which brings up the next question, ETA on when logging.apache.org will be coming around? Really, the config file thing is really a moot point until we hav

RE: Possible 1.2.8 release

Not a problem. But, I won't be able to apply the change until this evening. -Mark > -Original Message- > From: Ceki Gülcü [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 18, 2003 10:24 AM > To: Log4J Developers List > Subject: RE: Possible 1.2.8 release > > > > Given that the exi

RE: Indentation!!!

I didn't get home from work until after midnight, so needless to say, I did not check in the changes as promised. I will do it this evening though. -Mark > -Original Message- > From: Mark Womack > Sent: Monday, February 17, 2003 12:01 PM > To: 'Log4J Developers List' > Subject: RE: Inde

RE: Chainsaw improvement question - support for multiple sources

Scott, First, I want to say that any changes you want to implement for Chainsaw will be appreciated and reviewed for inclusion. We all love Chainsaw around here...:-) (and LF5 too...:-). Second, we have been kicking around the idea of having Chainsaw support "gui plugins" where each plugin confi

RE: Possible 1.2.8 release

Given that the existing JDBCAppender has other serious problems, I think fixing 14827 is a waste of time. In any case, I won't stand in your way. The following patch is likely to fix the problem. Index: src/java/org/apache/log4j/jdbc/JDBCAppender.java ===

RE: Possible 1.2.8 release

What about 14827/16998? Even if we are not going to use this class long term, it does have a serious memory leak, discovered by several people. Whether we like it or not, this appender seems popular. I vote to fix it. -Mark > -Original Message- > From: Ceki Gülcü [mailto:[EMAIL PROTECTE

Chainsaw improvement question - support for multiple sources

I am tinkering with some enhancements to Chainsaw that I hope will be accepted as part of the app when I'm done. I'm adding regexp-based filtering, saved settings, colorizing filters and some other stuff. No problem so far. I'm also adding multicast support for LoggingEvents broadcast using XMLL

RE: Configuration GUI & logging.apache.org

Howdy, >We haven't exhaustively checked this out everywhere. I'd like to see in >a logging.apache style project that we standardize on a config file >format (xml is more flexible, is it not?), and also, can we change >log4j.* and log4perl.* to log.*? > >Thoughts? Properties and XML files both h

RE: Configuration GUI & logging.apache.org

This may not be a good fit for log4* projects for a number of reasons (too heavyweight, etc). But consider that if the configuration file is xml with a known schema (or dtd, etc), then the individual implementations could use XSLT to produce a configuration file of their own specific formats at

RE: Configuration GUI & logging.apache.org

FYI. Currently log4net only supports an XML config file. Also it is not 100% compatible with the log4j config file. Some of this is due to different terminology (e.g. using the attribute 'type' rather than 'class' to specify the dynamically loaded object types), and some due to architectural differ

DO NOT REPLY [Bug 12366] - Cannot use Xerces 2.1.0 with XML configuration file because the file is not referred to as a URL by Log4J.

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

DO NOT REPLY [Bug 16516] - minutes instead of month ??

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

Configuration GUI & logging.apache.org

Hey folks, While working on a prelim version of the configuration gui we noticed a couple of things with respect to log4j/log4perl/c++ etc 1) Apparently log4perl and others support the property style config files, but not xml 2) in log4j the properties start like 'log4j.rootlogger', whereas perl

DO NOT REPLY [Bug 14933] - NDC stack not serializable

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

DO NOT REPLY [Bug 14926] - Throw an NullPointerException!

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/docs manual.html

ceki2003/02/18 09:15:18 Modified:docs Tag: v1_2-branch manual.html Log: Small editing changes Revision ChangesPath No revision No revision 1.33.2.4 +7 -8 jakarta-log4j/docs/manual.html Index: manual.ht

cvs commit: jakarta-log4j/docs HISTORY

ceki2003/02/18 09:00:03 Modified:docs Tag: v1_2-branch HISTORY Log: More editing on the HISTORY file. Revision ChangesPath No revision No revision 1.97.2.17 +3 -1 jakarta-log4j/docs/HISTORY Index: HISTO

cvs commit: jakarta-log4j/docs HISTORY

ceki2003/02/18 08:59:26 Modified:docs Tag: v1_2-branch HISTORY Log: Removed unintentional crap from the HISTORY file. Revision ChangesPath No revision No revision 1.97.2.16 +0 -5 jakarta-log4j/docs/HISTORY

RE: Possible 1.2.8 release

At 20:54 16.02.2003 -0800, you wrote: I did a quick review of open bugs. Besides the fix for #12366, I think we should consider fixes for: 14827/16998 - JDBCAppender memory leak. 11570/16170 - Null Pointer Exception in XMLLayout. Bugs 11570/16170 fixed. As well as 15599 reported by Scott

cvs commit: jakarta-log4j/src/xdocs documentation.xml download.xml

ceki2003/02/18 08:50:13 Modified:.Tag: v1_2-branch build.xml docs Tag: v1_2-branch HISTORY manual.html src/java/org/apache/log4j/helpers Tag: v1_2-branch Transform.java src/java/org/apache/log4j/net Tag:

DO NOT REPLY [Bug 11570] - XML Appender throws NullPointerException when logging null

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

DO NOT REPLY [Bug 16170] - NPE in XMLLayout

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

DO NOT REPLY [Bug 11570] - XML Appender throws NullPointerException when logging null

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/witness xmlLayout.null

ceki2003/02/18 08:39:01 Modified:tests/src/java/org/apache/log4j/xml Tag: v1_2-branch XMLLayoutTestCase.java Added: tests/witness Tag: v1_2-branch xmlLayout.null Log: Added test case in response to bug 11570. Revision ChangesPath No

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

hoju2003/02/18 07:50:20 Modified:.build.xml sunCodingConvention.xml src/java/org/apache/log4j/selector ContextClassLoaderSelector.java src/java/org/apache/log4j/servlet InitContextListener.java Init