I have looked around the documentation but have not seen anything that
discusses the ability to use Log4perl's convenience functions inside of
catalyst apps. Namely the shortcuts of TRACE, DEBUG(), INFO(), WARN(), ERROR(),
FATAL(), and ALWAYS. Call me lazy but I am trying to avoid doing things l
Websense Security Labs
http://www.WebsenseSecurityLabs.com
--
-Original Message-
From: Mike Schilli [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 9:37 PM
To: Mesdaq, Ali
Cc: log4perl-devel@lists.sourceforge.net
Subject: Re: [log4perl-devel
2007 8:46 PM
To: Mesdaq, Ali
Cc: Mike Schilli; log4perl-devel@lists.sourceforge.net
Subject: RE: [log4perl-devel] Initializing Question
On Tue, 17 Jul 2007, Mesdaq, Ali wrote:
> Great I am going to read the documentation on that now. Maybe you
> should rename easy mode to something more
Sunday, July 15, 2007 10:02 AM
To: Mesdaq, Ali
Cc: log4perl-devel@lists.sourceforge.net
Subject: Re: [log4perl-devel] Initializing Question
On Fri, 13 Jul 2007, Mesdaq, Ali wrote:
> The usual order that things are used in my case I write some
> functionality in a module and I might call anoth
Hello Everyone,
I had a question about initialization. Now this may be discussed in the
documents but I did not see it covered in depth and I had a long week so
I may also just be brain dead. My question is how can I initialize the
log4perl object so that its part of my object so I don't have to m
Love this module but first thing I noticed was incorrect handling with
logconfess. I checked out the source and I think I see the reason
explained below.
Bug Description:
Calling logconfess(); only prints and records the log message passed to
logconfess() and the initiator of my module.
Setup:
T
