I suggest using commons-logging as your wrapper around log4j.
Make sure to code it for optimization:
if (log.isDebugEnabled())
{
log.log("Message");
}
Things like that.
Cheers.
________________________________
From: Rachel Primrose [mailto:[EMAIL PROTECTED]
Sent: Monday, December 10, 2007 4:00 PM
To: axis-user@ws.apache.org
Subject: Re: log4j use in skeletons
The only advice I would give is make sure you use the correct levels,
axis2 outputs a lot of debug and info and at some point, perhaps when
you deploy, you may want to lower the amount coming out.
Apart from that, it's just log4j.
On Dec 11, 2007 10:22 AM, Michael Potter <[EMAIL PROTECTED]> wrote:
Axis2 Crew,
I am interested in adding log4j logging in my hand coded
*skeleton classes.
Does anyone have some hard learned lessons that I can benefit
from?
--
Michael Potter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Kind regards,
Rachel Primrose
E: [EMAIL PROTECTED]
M: 021 969 728
