Paul Smith wrote:
services.LoggingService.logforj.log4j.rootCategory = DEBUG, logforj is analogous to (I think): log4j.rootCategory = DEBUG, logforj
Hmm, so I could probably pull the content of log4.properties into Turbine.properties if I wanted to :-)
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.
There's every chance the next version of Turbine will have abolished the logging service too, for what I've read. Besides, I don't want to have to remember to use one API in the Turbine parts of my project and another elsewhere... ;-)
L.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
