Thanx Curt,
I have included <log4cxx/patternlayout.h> and it worked.Currently I
am facing a new problem.I was trying to access Ostream *os variable to get
the logging string.But I failed to get the string.I have explicitely set the
immediateFlush variable as FALSE.
As you said OStream *os will be removed very soon so is there any
other way by which I can get the logging string in a custom appender??
Also please tell me is there any way by which at run time we can
block an appender which is attached to the Root Logger.
Regards
Prosenjit Sinha
Project Engineer
-----Original Message-----
From: Curt Arnold [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 10:55 PM
To: Log4CXX User
Subject: Re: Custom appender (was Re: Building log4cxx 0.9.7 with MinGW and
MSYS (no cygwin))
On Dec 7, 2004, at 6:20 AM, Prosenjit Sinha wrote:
>
> Thanx Curt,
> The appender class which I am going to create will only be used for
> obtaining the logging string from the OStream *os variable(I have
> found out
> only this mechanism by which I can get the logging string in my own
> class....is there any other method for it).This logging string will be
> used
> for some other purpose but not for logging.
> I have tried to use "log4cxx::LayoutPtr layout(new
> log4cxx::PatternLayout("%m %n\n"));" --But it is giving me an error
> that
> PatternLayout is not defined in log4cxx.
>
>
The implementation of WriterAppender is changing and will no longer
contain an std::ostream. The new form might work better for you.
Hopefully will have it in CVS in a day or two.
Have you included <log4cxx/patternlayout.h>?
Confidentiality Notice
The information contained in this electronic message and any attachments to
this message are intended
for the exclusive use of the addressee(s) and may contain confidential or
privileged information. If
you are not the intended recipient, please notify the sender at Wipro or [EMAIL
PROTECTED] immediately
and destroy all copies of this message and any attachments.
