On 26/10/2007, at 5:26 AM, Joshua ChaitinPollak wrote:
So, avoiding my earlier question, I enabled the jul bridge using JULLog4jBridge.assimilate();, but it seems to set all JUL logging at TRACE level. Could this be because I called .assimilate() before I configured logging? What else would cause this? We set our root logger to WARN, so I was a bit surprised.
The assimilation process needs to set the jul side of things to trace, so that ALL the events get routed across to log4j. After they arrive into the log4j bus, the events _should_ be treated like any normal log4j event and obey the level filtering. I wouldn't think configuring log4j after assimilation would make much difference.
If you had the time, crafting a unit test based on the other unit tests in the bridge project would be most useful to demonstrate a problem if there was one.. ?
Perhaps an example of your log4j configuration process (config file) and an example of the TRACE level logging event being output to a file?
cheers, Paul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
