I can't speak to the state of the JDBC-based appenders. The JDBCReceiver should be ready for entry into core soon - the only significant change I need to make (as Raymond has suggested) is to retrieve the datasource using org.apache.log4j.jdbc.ConnectionSource. The other question is how should the receiver handle database exceptions. Currently the stack trace is printed.
It's a necessarily complicated beast in a sense because the user provides the query required to retrieve the events, which appears daunting but is relatively straightforward. We use it to retrieve events from a table in SQL Server. -----Original Message----- From: Ceki Gülcü [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 5:48 AM To: Log4J Developers List Subject: Re: JDBCReceiver At 02:02 PM 12/9/2003 -0800, Scott Deboy wrote: >Is there a reason why JDBCReceiver couldn't be moved from sandbox to >core? I recently made some fixes that improve it's performance pretty >dramatically (it was re-appending events it had previously seen).. > >For folks who have no way to send events via the network but can write >to a database, (and would like to use Chainsaw V2), it's really handy. >We use it here at work extensively to help in tracking down problems in >ASP code...ug > >Opinions? Does that include PreparedStatementAppender and co.? Do you feel that the code is or will be ready to enter the core? -- Ceki Gülcü For log4j documentation consider "The complete log4j manual" ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
