Hello Peter!
I'm writing two different answers to your mail: to dev@ and to users@
This one is to users@
PS> ... log4j configuration ...
PS> Doing only setLoggerManagerConfiguration() doesn't do the trick.
PS> Fortress continues to use logkit
Yes, I see ContextManager creates a LogKitLoggerManager.
Maybe we'll patch ContextManager to be smarter, meanwhile...
PS> Using setLoggerManager() with preconfigured Log4JLoggerManager doesn't look
PS> much different from what I am doing now - configuring log4j directly
PS> using PropertyConfigurator.
<disclaimer>
I'm not good at this, but will try to help where I can :-)
</disclaimer>
Do I get you right that you're using Log4JLoggerManager vs
Log4JConfLoggerManager?
There is no much difference really.
If you're already using Log4JLoggerManager I see no reason for
you to switch to Log4JConfLoggerManager.
PS> The only difference is that I am not
PS> using LoggerManager interface to perform the configuration. My be it
PS> would be better to use this interface although I am not familiar with
PS> avalon configuration loading API yet.
It's really very easy. Just use
o.a.a.framework.configuration.DefaultConfigurationBuilder
a piece of cake ;-)
PS> If I do it like this, will my log
PS> files configured in the xlog file be created under the fortress's work
PS> directory configured using "FortressConfig.setWorkDirectory()" ?
Unfortunantly no. You'll have to let Log4J know about the directories
you want it to write logs too separately.
Regards, Anton :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
