> > Yeah, but how does that translate into Log4j categories? It sounds > > like the answer is 'directly' -- i.e. I'd use > > 'log4j.category.system=...' in log4j.properties. >
I believe it is definately directly. I've just recently been through this sort of thing, wanting our Turbine app just to use Log4j (used to use Turbine logging->log4j). Turns out that Log4J has some smarts in it. After I saw this in the Turbine CVS: http://cvs.apache.org/viewcvs.cgi/jakarta-turbine-2/src/java/org/apache/turb ine/services/logging/Log4JavaLogger.java?rev=1.3&content-type=text/vnd.viewc vs-markup Setting: services.LoggingService.logforj.log4j.rootCategory = DEBUG, logforj is analogous to (I think): log4j.rootCategory = DEBUG, logforj Log4J actually has some methods in it (PropertyConfigurator) that "finds" the keys, so you can pretty much prefix stuff in front of the 'log4j.' and it'll still find it. Handy. My recommendation is to leave Turbine's logging wrapper aside and just use Log4J for you own app's logging. Turbine's logging is great and simple to get started, but if you need extra features (like Daily/Weekly rotation) you'll need to go straight through to work with Log4J. cheers, Paul Smith -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
