DBAppener2 was added to CVS by mistake. You can ignore it/delete it.
DBAppender is stable and tested. I wouldn't qualify it as industrial strength because it reportedly behaves badly when the database is bounced/recycled. We need to test it so that it can reconnect to the db after a temporary failure, much like SocketAppender.
I am thinking of testing this with mock JDBC Connections. Does anyone know a better way to fake DB errors in tests?
At 08:04 PM 2/11/2005, Curt Arnold wrote:
What is org.apache.log4j.db.DBAppender2 and why would I use it instead of DBAppender? What is the status of the org.apache.log4j.db? Is it stable enough to consider porting it to log4cxx to replace its ODBCAppender?
-- Ceki G�lc�
The complete log4j manual: http://www.qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
