Good catch on the package name. So, reading your post on the xml validating issue, it looks like you did get something up and running that could be used to validate log4cxx xml? Validating would be nice.
What I probably need more than anything is documentation on the API useage and configuration. Would you recommend the book "The complete manual - log4j"? I'm spending a lot of time just debugging the code to figure out how an API works... BTW, keep up the good work - this stuff kicks butt! -----Original Message----- From: Curt Arnold [mailto:[EMAIL PROTECTED] Sent: Thursday, April 20, 2006 3:27 PM To: Log4CXX User Subject: Re: help: RollingFileAppender (xml configuration?) On Apr 20, 2006, at 11:16 AM, B Moody wrote: > > Hold that thought. I figured out the problem. I assumed it would > create the > output directory. Once I created it, it worked fine. Thanks again > for the > help! > > Brian Creating necessary directories was recently added to log4j (http:// issues.apache.org/bugzilla/show_bug.cgi?id=9150). Apparently the behavior hasn't been ported over to log4cxx. I've logged LOGCXX-134 (http://issues.apache.org/jira/browse/LOGCXX-134) so that this behavior will be ported over. I did notice in your sample configuration file that "rolling" was missing from your class name for SizeBasedTriggeringPolicy. I believe the package name is currently ignored by log4cxx, but that might change so that both "org.apache.log4j.RollingFileAppender" and "org.apache.log4j.rolling.RollingFileAppender" could appear in configuration files (and they have radically different configurations). p.s.: There was some work in the logging services sandbox to define a validatable XML configuration format that would not depend on log4j class names, but that activity is currently on hold (http:// marc.theaimsgroup.com/?l=apache-logging-general&m=113981617314339&w=2)
