Hmmmm, very interesting, didnt realise that commons-logging was
problematic, just that I avoided it before because I didnt want to
introduce yet another library dependency for logging; which is so low
level that I don't think the logging stack ever change in a project
lifetime.
About slf4j, what makes it different compared to commons-logging? Wont
it have class loading issues as well?
I guess a big plus point is that it comes with Wicket anyway, so I might
as well use it.
Regards,
Lester
Igor Vaynberg wrote:
i wouldnt, commons logging, aka clogging, has been a bane of web
applications for a long time...
wicket uses slf4j, why dont you do the same? still declaring your
loggers static.
-igor
On Wed, Nov 18, 2009 at 9:07 PM, Lester Chua <[email protected]> wrote:
I think I'll use this then. I was reluctant to because of the need to
introduce yet another library (some examples used this).
Thanks!
Lester
James Carman wrote:
Commons Logging?
On Wed, Nov 18, 2009 at 11: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]
---------------------------------------------------------------------
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]
