Many thanks to both you and James.
I will use slf4j (with log4j underlying) and static the logger.
Regards,
Lester
Igor Vaynberg wrote:
their website is a good source of information, afair the basic
difference that unlike clogging slf4j uses compile-time binding
instead of run-time binding of
By the way (not to start a flame war or anything), but "clogging" has
been working just fine for us. We use it along with SLF4J using the
adapter, We've had no problems at all. Don't get me wrong, I am
aware of the issues with Commons Logging and I've argued for us to
change the way it works to
their website is a good source of information, afair the basic
difference that unlike clogging slf4j uses compile-time binding
instead of run-time binding of api to impl thus avoiding classloader
hell.
-igor
On Wed, Nov 18, 2009 at 9:21 PM, Lester Chua wrote:
> H, very interesting, didnt rea
SLF4J would work just fine, too. Either way, you should declare them
static. That avoids serializing them altogether.
On Thu, Nov 19, 2009 at 12:09 AM, Igor Vaynberg wrote:
> i wouldnt, commons logging, aka clogging, has been a bane of web
> applications for a long time...
>
> wicket uses slf4j
H, 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, w
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 wrote:
> I think I'll use this then. I was reluctant to because o
no
-igor
On Wed, Nov 18, 2009 at 9:05 PM, Lester Chua wrote:
> 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
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 wrote:
Hi,
I'm using log4j as my logging tool.
But when I add
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
declare your logger static
-igor
On Wed, Nov 18, 2009 at 8:11 PM, Lester Chua 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
Commons Logging?
On Wed, Nov 18, 2009 at 11:11 PM, Lester Chua 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 {
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()
12 matches
Mail list logo
