Rodney Schneider wrote:
I am pretty sure you should be able to do this...
That's what I like to hear :)
Yeah, that should do the trick. The only facility you will need is "system". If you want the SQL statements logged, you can also enable the "sql" facility, but I would recommend P6Spy for this. My settings for this (I use log rotation) are: -------------- services.LoggingService.system.destination.file=/logs/turbine.log services.LoggingService.system.file.size=1048576 services.LoggingService.system.file.backups=5 services.LoggingService.system.className=org.apache.turbine.services.logging.Log4JavaLogger services.LoggingService.system.level=DEBUG --------------
What happens if I don't specify the ...destination.file property? That should be configured through the log4j.properties. In fact, everything but the className should ideally...
Torque, Fulcrum and the ComponentService are all configured from a log4j.properties file. You will find this in the latest TDK release (tdk-2.2_01.tar.gz) or see Scarab issue TDKS11.
If I read your posting on the dev list right, there's no code changes in 2.2_01, right? I.e. this should all work for 2.2 as well?
All Turbine generated logging goes through the "system" and "sql" facilities of the LoggingService configured in TurbineResources.properties.
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.
L.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
