Re: WicketTester and org.slf4j.LoggerFactory and org.slf4j.Logger not serializable

2009-07-28 Thread Reinhard Nägele
If you use slf4j 1.5.3 or newer, serialization should just work fine. See http://www.slf4j.org/faq.html#declared_static Reinhard Jeremy Thomerson schrieb: Your logger instances should either be transient or static - so that they are not serialized. -- Jeremy Thomerson

Re: WicketTester and org.slf4j.LoggerFactory and org.slf4j.Logger not serializable

2009-07-28 Thread David Brown
Hello Jeremy, thanks for the reply. Painfully obvious now (doh!). David. - Original Message - From: Jeremy Thomerson jer...@wickettraining.com To: users@wicket.apache.org Sent: Monday, July 27, 2009 7:52:57 PM GMT -06:00 US/Canada Central Subject: Re: WicketTester and

WicketTester and org.slf4j.LoggerFactory and org.slf4j.Logger not serializable

2009-07-27 Thread David Brown
Hello, I have a Wicket 1.4rc4 application with a homegrown set of JDBC DAO classes: basic JDBC Connection and various methods for SQL queries and transactions. And Connection pooling is imported into the same JDBC DAO class and works well against the JUnit TestCases. The JUnit TestCases for the

Re: WicketTester and org.slf4j.LoggerFactory and org.slf4j.Logger not serializable

2009-07-27 Thread Jeremy Thomerson
Your logger instances should either be transient or static - so that they are not serialized. -- Jeremy Thomerson http://www.wickettraining.com On Mon, Jul 27, 2009 at 8:01 PM, David Browndbr...@sexingtechnologies.com wrote: Hello, I have a Wicket 1.4rc4 application with a homegrown set of