Thanks,
I was wondering about that since it seems to get away from
Serialization. But I do not understand Wicket internals when it comes to
clustering. Will this approach impact the clustering facility supported
by Wicket out of box?
Lester
Igor Vaynberg wrote:
declare your logger static
-igor
On Wed, Nov 18, 2009 at 8:11 PM, Lester Chua <[email protected]> wrote:
Hi,
I'm using log4j as my logging tool.
But when I add log4j loggers into my components, I get serialization issues.
Wicket gives serialization errors because of the logger.
E.g.
class SomeForm extends Form {
Logger logger = LogManager.getLogger(SomeForm.class);
public void someMethod() {
logger.debug("Some Message");
}
}
This class will give an serialization error. Wicket complains about
serializing logger.
Is there a recommended way to do logging in wicket to avoid this?
Thanks in advance.
Lester
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]