cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/help release-notes.html

sdeboy 2004/05/20 23:27:31 Modified:src/java/org/apache/log4j/chainsaw/help release-notes.html Log: updated release notes to include comment about xml decoder npe fix Revision ChangesPath 1.6 +5 -2 logging-log4j/src/java/org/apache/log4j/chainsaw/help/release

cvs commit: logging-log4j/src/java/org/apache/log4j/xml UtilLoggingXMLDecoder.java XMLDecoder.java

sdeboy 2004/05/20 23:19:32 Modified:src/java/org/apache/log4j/xml UtilLoggingXMLDecoder.java XMLDecoder.java Log: Preventing null exception in utillogging decoder reverted support for xml files with xml declaration, doctype and eventSet root node requi

cvs commit: logging-log4j/src/java/org/apache/log4j/xml Log4jEntityResolver.java XMLDecoder.java

sdeboy 2004/05/20 22:38:28 Modified:src/java/org/apache/log4j/xml Log4jEntityResolver.java XMLDecoder.java Log: Added support in XMLDecoder for xml documents conforming to log4j.dtd which include the XML declaration and doctype declaration Assigning excep

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/vfs FileObjectTable.java

psmith 2004/05/20 21:53:01 Modified:src/java/org/apache/log4j/chainsaw/vfs FileObjectTable.java Log: fixed bug where if the row was selected, the alignment of some columns was incorrect. Thanks to Scott for picking that one up. Revision ChangesPath 1.3 +3 -5

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/vfs FileObjectTable.java

psmith 2004/05/20 21:24:16 Modified:src/java/org/apache/log4j/chainsaw/vfs FileObjectTable.java Log: Table looks much nice with row striping and alignment. Also added the sort feature. Remind me to buy Claude & Scott an extra beer. Nice and easy. Revision Changes

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/vfs DirectoryListTableModel.java

psmith 2004/05/20 21:23:23 Modified:src/java/org/apache/log4j/chainsaw/vfs DirectoryListTableModel.java Log: Implemented SortTableModel for extra sort goodness. Hmmm... Sortable... Revision ChangesPath 1.3 +81 -2 logging-log4j/src/java

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/vfs FileSystemTreePanel.java

psmith 2004/05/20 21:22:46 Modified:src/java/org/apache/log4j/chainsaw/vfs FileSystemTreePanel.java Log: subtle tree call to get it to display correctyl sometimes. Revision ChangesPath 1.5 +1 -0 logging-log4j/src/java/org/apache/log4j/

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/vfs VFSPlugin.java

psmith 2004/05/20 21:22:10 Modified:src/java/org/apache/log4j/chainsaw/vfs VFSPlugin.java Log: If the user has elected to auto load all the local file systems, we should honour that. Revision ChangesPath 1.6 +31 -15 logging-log4j/src/java/org/apache/log4j/chai

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/vfs VFSPluginPreferenceModel.java

psmith 2004/05/20 21:21:30 Added: src/java/org/apache/log4j/chainsaw/vfs VFSPluginPreferenceModel.java Log: Initial version of this plugins preference. Of course at the moment you can't change the values yet, and they wouldn't get saved anyway...

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/vfs VFSPlugin.java

psmith 2004/05/20 16:13:50 Modified:src/java/org/apache/log4j/chainsaw/vfs VFSPlugin.java Log: child directories are now located 'lazily', that is, only when you explicitly select the folder in the tree. This defers the cost of finding out the children until you need it, maki

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/vfs VFSUtils.java

psmith 2004/05/20 16:11:14 Modified:src/java/org/apache/log4j/chainsaw/vfs VFSUtils.java Log: removed (moved) a method into a more appropriate class, it is not really a utility method, as it is really specific to a particular function. Revision ChangesPath 1.2 +

cvs commit: logging-log4j/src/java/org/apache/log4j/chainsaw/messages MessageCenter.java

psmith 2004/05/20 16:09:57 Modified:src/java/org/apache/log4j/chainsaw/messages MessageCenter.java Log: Changed so that only DEBUG messages are shown in the MessageCenter when the log4j.debug property has been set to true. Revision ChangesPath

RE: cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialec t mssql.sql

At 06:41 PM 5/20/2004, you wrote: How is it configured to not log that info (since it is supposed to be expensive)? Look at the code in DBAppender. It should make it clear. Also am I curious why you write "?" instead of just leaving it null. That's because the locationInfo fiels in LoggingEvent is

RE: cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialec t mssql.sql

Title: RE: cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialec t mssql.sql How is it configured to not log that info (since it is supposed to be expensive)? Also am I curious why you write "?" instead of just leaving it null. James Stauffer -Original Message- From: Cek

RE: [logging] Thanks All...

At 06:34 PM 5/20/2004, Noel J. Bergman wrote: > ( Let's hope some Velocity folk can help out next: Shouldn't: [javac] /data3/gump/jakarta-velocity/bin/src/org/apache/velocity/runtime/log/SimpleL og4JLogSystem.java:119: cannot resolve symbol [javac] symbol : method setPriority (org.apache.l

RE: cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialec t mssql.sql

Indeed. If no location info is desired or unavailable, it will still be written as "?". At 06:33 PM 5/20/2004, you wrote: Why did you add them as non-null? Will they always be written? James Stauffer -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTEC

RE: cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialec t mssql.sql

Title: RE: cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialect mssql.sql Why did you add them as non-null?  Will they always be written? James Stauffer -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 20, 2004 11:19 AM To: [EMAI

cvs commit: logging-log4j/src/java/org/apache/log4j/db/dialect mssql.sql

ceki2004/05/20 09:19:01 Modified:src/java/org/apache/log4j/db/dialect mssql.sql Log: Added necessary fields to support LocationInfo. Revision ChangesPath 1.2 +4 -0 logging-log4j/src/java/org/apache/log4j/db/dialect/mssql.sql Index: mssql.sql

State of DBAppender

Hello all, The DBAppender/DBReceiver pair which is currently checked in CVS has the following qualities: - Support for various types of connection sources o JDBC driver obtained through DriverManager, o DataSource obtained through direct instantiation o DataSource obtained through JNDI - Logg

cvs commit: logging-log4j/tests/input/db .cvsignore

ceki2004/05/20 08:48:14 Modified:tests/input/db .cvsignore Log: - tests/input/db/db.properties should not be CVS managed. Removing it. Revision ChangesPath 1.3 +1 -0 logging-log4j/tests/input/db/.cvsignore Index: .cvsignore ==

cvs commit: logging-log4j/tests/src/java/org/apache/log4j/db BindDataSourceToJNDIAction.java DBReeceiverTest.java

ceki2004/05/20 08:47:30 Modified:src/java/org/apache/log4j/spi LocationInfo.java tests/src/java/org/apache/log4j/db BindDataSourceToJNDIAction.java Removed: tests/input/db db.properties tests/src/java/org/apache/log4j/db DBR

cvs commit: logging-log4j/src/java/org/apache/log4j/net JMSAppender.java

ceki2004/05/20 08:38:00 Modified:src/java/org/apache/log4j/db DBReceiver.java ConnectionSource.java DBAppender.java DataSourceConnectionSource.java JNDIConnectionSource.java DriverManagerC

cvs commit: logging-log4j/src/java/org/apache/log4j/db DBReceiver.java

ceki2004/05/20 07:53:16 Modified:src/java/org/apache/log4j/db DBReceiver.java Log: lastId should start at 0 not 1. Revision ChangesPath 1.5 +1 -1 logging-log4j/src/java/org/apache/log4j/db/DBReceiver.java Index: DBReceiver.java ==

[logging] Thanks All...

Now this is a pretty picture: http://lsd.student.utwente.nl/gump/project_fixes.html Thanks for all the effort around getting this back to green! ( Let's hope some Velocity folk can help out next: http://lsd.student.utwente.nl/gump/project_todos.html ) regards, Adam -- Experience the Un

cvs commit: logging-log4j/tests/resources jndi.properties

ceki2004/05/20 05:05:09 Added: tests/resources jndi.properties Log: Testing JNDIConnectionSource with actual JNDI context. This test requires the existence of a JNDI provider, for example the "File System Service Provider 1.2 Beta 3". Revision ChangesPath

cvs commit: logging-log4j/src/java/org/apache/log4j Priority.java

ceki2004/05/20 04:49:46 Modified:src/java/org/apache/log4j Priority.java Log: It should not be possible to create Priority instances. Revision ChangesPath 1.28 +1 -2 logging-log4j/src/java/org/apache/log4j/Priority.java Index: Priority.java ==

cvs commit: logging-log4j/tests/src/java/org/apache/log4j/db BindDataSourceToJNDIAction.java

ceki2004/05/20 04:49:08 Modified:tests/input/db read-with-pooled-datasource1.xml read-with-datasource1.xml src/java/org/apache/joran ExecutionContext.java testsbuild.xml build.properties.sample src/java/org/apac

Re: [logging][PROPOSAL] a solution to incompatibility between log4j versions

The strategy we adopted when renaming Category as Logger and Priority as Level at the time log4j 1.2 was released, consisted of having Logger extending Category, and Level extending Priority. This is quite a non-intuitive approach but with solid technical reasons behind it. [1] http://www.geocrawle

Fwd: Re: [logging][PROPOSAL] a solution to incompatibility between log4j versions

Paul, You may find the following comments by Adam R. B. Jack relevant to the selective compilation problem we are facing with VFS. I am not sure whether Ant selectors are applicable to our situation or not, just forwarding the info. List-Unsubscribe: List-Subscribe: