You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Curt Arnold <ca...@apache.org> on 2005/02/11 20:04:10 UTC
DBAppender2?
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?
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: DBAppender2?
Posted by Ceki Gülcü <ce...@qos.ch>.
No doubt that DBAppender should support Derby. Having a lightweight DB is
certainly the way to go for testing purposes.
Has anyone already used mock objects to fake JDBC connection failures?
At 09:17 PM 2/11/2005, you wrote:
>Have you considered using Apache Derby
>(http://incubator.apache.org/derby/) in the tests? Just a question, not a
>recommendation. I know it would add yet another dependency to the build
>(and an incubated one at that), but it should allow you to test against a
>"real" database without a lot of the setup issues.
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: DBAppender2?
Posted by Curt Arnold <ca...@apache.org>.
Have you considered using Apache Derby
(http://incubator.apache.org/derby/) in the tests? Just a question,
not a recommendation. I know it would add yet another dependency to
the build (and an incubated one at that), but it should allow you to
test against a "real" database without a lot of the setup issues.
On Feb 11, 2005, at 1:17 PM, Ceki Gülcü wrote:
>
> 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?
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: DBAppender2?
Posted by Ceki Gülcü <ce...@qos.ch>.
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org