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
Scott Deboy wrote:
Here are my comments:
1 - We should leave in support for configurable column names. There
are folks out there already writing logging events to tables - and
likely using this table or tables as a common logging infrastructure
in their enterprise across systems. Allowing JDBCAp
Here are my comments:
1 - We should leave in support for configurable column names. There are folks out
there already writing logging events to tables - and likely using this table or tables
as a common logging infrastructure in their enterprise across systems. Allowing
JDBCAppender to write
After studying both PreparedStatementAppender vs. JDBCAppenderPlus, I would
like to build on mostly PreparedStatementAppender for the DBAppender to be
included in the next version of log4j.
My preference goes to PreparedStatementAppender over JDBCAppenderPlus
because of its simplicity although
Hello Danko,
Your generous offer to contribute your JDBCAppender to the log4j project is
well appreciated. As you have observed, Raymond DeCampo, has offered to
contribute his PreparedStatementAppender. I will take the next few hours to
study both code bases. I very much hope to engage both of
>You could pass a parameter to the extended localisation parameter. You
>can for example write:
>log4j.appender.stdoutAppender.layout.ConversionPattern=[%c] - \
>(%Fx{DEBUG}:%Lx{DEBUG}) %p [%t]: %m%n
>I hope you find the above convincing.
Yes, this is convincing. Didn't know you can pass paramet
At 08:55 PM 4/20/2004, Ognjen Kavazovic wrote:
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
Could someone please give me a clue to which script/whatever is generting
these mails? Are they run by some cron-process?
The reason for asking, is that I'd love to have this stuff for our
in-house development-environement too..!
On Sun, 25 Apr 2004 [EMAIL PROTECTED] wrote:
| +--
