pulling hair out
tried everything, this stuff is just copied out of the docs. I am expecting
to get a file "example.log", console output is not possible in this
situation. If I change the path to the property file it fails, as expected.
So at least I believe that is getting read in. I have tried specifying full
path to example.log also. Tried LOG4CXX_DEBUG.
here is some of the code:
extern "C" UINT __stdcall ValidateActuateiServerSettings(MSIHANDLE hInstall)
DWORD ServerPortLen = MAX_PATH;
LoggerPtr rootLogger = Logger::getRootLogger();
LOG4CXX_INFO(rootLogger, "Entering ValidateActuateiServerSettings");
RollingFileAppender is stubbed out in log4cxx at the moment in
anticipation of porting over the log4j 1.3 new Rolling File framework.
Try using a FileAppender. Should have RFA's on-line within the week.
Nope, still no logfile, but thanks! I had forgotten to even suspect the
logging code, I had assumed it was my mistake.
log4j.rootLogger=debug, stdout, R
# Pattern to output the caller's file name and line number.
log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n
but still no love
"Curt Arnold" <[hidden email]> wrote in message
> RollingFileAppender is stubbed out in log4cxx at the moment in
> anticipation of porting over the log4j 1.3 new Rolling File framework.
> Try using a FileAppender. Should have RFA's on-line within the week.