On Fri, Feb 22, 2008 at 11:02 AM, Curt Arnold <[EMAIL PROTECTED]> wrote:
> > On Feb 22, 2008, at 3:30 AM, Andreas Grund wrote: > > > Hi, > > > > I just downloaded and tests the log4j 1.2.15 version and I saw, that > > the > > JoranConfigurator is not back-ported. Are there any plans to do so? > > I sk, > > because I read in the comments, that the JoranConfigurator shall be > > more > > powerfull then the DOMConfigurator... > > > > Greetings, > > Andreas > > > > > > Nope the JoranConfig is a dead end here. We've enhanced the log4j > 1.2.x DOMConfigurator to delegate unrecognized content to the > containing object which gives us the most significant benefit of the > JoranConfig, the ability to have nested content. The long term > solution is to migrate to an established configuration framework and > translate legacy formats prior to processing. > FYI, logback is using JoranConfigurator and unlike log4j it does support resolving placeholders in the xml config from values set at-runtime. http://logback.qos.ch/manual/joran.html Maarten > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
