To whom it may engage...
This is an automated request, but not an unsolicited one. For help
understanding the request please visit
http://gump.apache.org/nagged.html,
and/or contact [EMAIL PROTECTED]
Project log4j-tests has an issue affecting its community integration, and has been
ou
also...make sure you register you contributions with bugzilla as well (not just with
this mailing list).
Otherwise, the contributions will likely get lost.
-Original Message-
From: Ceki GÃlcà [mailto:[EMAIL PROTECTED]
Sent: Tue 4/20/2004 11:31 AM
To: Log
Ceki Gülcü wrote:
Hi Scott,
Will you be improving JDBCAppender in any way? I have been quite unhappy
with it in the past but have not had a chance to work on it for a long
time...
Ceki,
I'd like to propose the PreparedStatementAppender as a replacement for
JDBCAppender, even if it is tooting
It's unfortunate that we are targeting a minimum of JDK 1.2, as in 1.3 this
could all be done with the java.util.Timer and java.util.TimerTask...
Nice though, Ceki! Good work.
Paul Smith
-Original Message-
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: 4/20/04 8:04 PM
Subject: c
At 09:37 PM 4/20/2004, Scott Deboy wrote:
To clarify how Chainsaw avoids duplicates, ChainsawCyclicBufferTableModel
maintains the collection of IDs which exist in the table model's
unfiltered list. If an event is received which already has that ID, the
event isn't added to the model.
This is a
To clarify how Chainsaw avoids duplicates, ChainsawCyclicBufferTableModel maintains
the collection of IDs which exist in the table model's unfiltered list. If an event
is received which already has that ID, the event isn't added to the model.
This is a fragile workaround - would like to rely on
Title: Message
Log4J
Developers,
Sorry for the cross
post but since LoggingEvent properties are prerelease I think this may be the
better forum.
I am interested in
working with the newly available Properties of LoggingEvent and was wondering
how to populate them. I noticed that the Appe
Thanks Ceki,
I haven't had time to work on JDBCAppender and I doubt I will.
I'll update the docs to reflect support for properties in the layout. Chainsaw relies
on the IDField param as the column used to uniquely identify rows (the 'idfield' param
is used as the ID column in Chainsaw).
The S
Hi Ceki,
thanks for your response. My comments:
1. callerFQCN: what you said makes sense. My work around was due to the fact
that the wrapper class wasn't mine, but an Avalon Project's Log4JLogger. So
the bug is really an Avalon bug...I'll submit it to them. thanks!
2. Level/PatternConverter: I
ceki2004/04/20 11:47:59
Modified:src/java/org/apache/log4j/scheduler Scheduler.java
tests/src/java/org/apache/log4j/scheduler SchedulerTest.java
Log:
Schduler is now pretty heavily tested.
Events can be scheduled and scheduled events can be deleted.
Revisio
Hi Scott,
No objections to move JDBCReceiver and DeCampo's data source access code to
the jdbc package in log4j proper. Changes can be added if the need arises.
Will you be improving JDBCAppender in any way? I have been quite unhappy
with it in the past but have not had a chance to work on it f
ceki2004/04/20 10:19:51
Modified:docs HISTORY
src/java/org/apache/log4j/spi LoggerRepository.java
src/java/org/apache/log4j Hierarchy.java
PropertyConfigurator.java
Log:
- Added the "isPristine" falg to LoggerRepository.
Hello Ognjen,
Please see my comments below.
At 05:57 PM 4/20/2004, Ognjen Kavazovic wrote:
Hello,
I would like to propose and contribute a couple of relatively minor features
to the current code base, but am not finding any documentation as to how I
should go about getting the features approved
Hello,
I would like to propose and contribute a couple of relatively minor features
to the current code base, but am not finding any documentation as to how I
should go about getting the features approved and then submitting the patch.
Could someone point me to the right doc or let me know what I
ceki2004/04/20 03:04:04
Added: src/java/org/apache/log4j/scheduler Scheduler.java Job.java
tests/src/java/org/apache/log4j/scheduler SchedulerTest.java
Log:
Started work on a global task scheduler. It will allow multiple watchdogs
to share a single scheduler
ceki2004/04/20 03:03:58
logging-log4j/tests/src/java/org/apache/log4j/scheduler - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ceki2004/04/20 03:03:58
logging-log4j/src/java/org/apache/log4j/scheduler - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ceki2004/04/20 03:02:31
Modified:docs HISTORY
src/java/org/apache/log4j/helpers LogLog.java
src/java/org/apache/log4j PropertyConfigurator.java
Log:
- Removed support for the deprecated property "log4j.configDebug". [**/D]
Revision Change
ceki2004/04/20 02:53:57
Modified:src/java/org/apache/log4j/chainsaw LogUI.java
Log:
Removed two unused imports
Revision ChangesPath
1.85 +0 -2 logging-log4j/src/java/org/apache/log4j/chainsaw/LogUI.java
Index: LogUI.java
==
ceki2004/04/20 02:53:25
Modified:src/java/org/apache/log4j/lf5/util DateFormatManager.java
Log:
Corrected an inffective assingment instruction.
Revision ChangesPath
1.2 +1 -1
logging-log4j/src/java/org/apache/log4j/lf5/util/DateFormatManager.java
Inde
ceki2004/04/20 02:51:24
Modified:examples/src/factor NumberCruncherServer.java
Log:
- Jalopized.
- Corrected an access type warning by Eclipse.
Revision ChangesPath
1.2 +69 -59logging-log4j/examples/src/factor/NumberCruncherServer.java
Index: NumberC
21 matches
Mail list logo
