Logging configuration

[Laurie Harper]

OK, before I start: I know logging has been a contentious issue lately; I'm not interested in where Turbine is or should be going in the future, just in what I can do with it today ;-) I'm using Turbine 2.2 release.

My objective it to unify, as far as possible, all logging from my application. Ideally I'd like to get it all routed through Log4J, use a single configuration file to control logging for all components, and write all log output to a single common file.

So, questions:

1) can I configure Turbine to use Log4J for all logging? If so, how do I do that? Just change all the services.LoggingService.*.className entries in Turbine.properties to o.a.t.services.logging.Log4JavaLogger?

2) how do I defer all further logging configuration to a central log4j.properties config file? Can I set services.LoggingService.loggingConfig to a file name, or to null so Turbine wont do any logging configuration itself?

3) once everything is going through Log4J how do I control Turbine generated logging from the generic log4j.properties file? I know how Log4J works, just not how Turbine would be using it. Does Turbine use class names as logging categories? Or would I have to filter based on the facility names in Turbine.properties?

If there's any documentation on this (other than the comments in Turbine.properties) feel free to point me at it and I can come back with any questions it doesn't answer :-)

L.


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>