> I need to review PropertyConfigurator to see if we can modify > it to support > plugins. I think it is doable, just haven't had time to look at it.
That would be neat although not essential. I wasn't sure if the Log4J community was moving forward to eventually disgarding the properties file. I personally prefer the XML file, but is it ok for Chainsaw to require that the community use a config in XML? > Can you just define -Dlog4j.configuration=[your file name here] in the > command line to start Chainsaw? Log4j will initialize itself > using the > file, which can contain the configuration for the reciever(s) and > ChainsawAppender. *Doh*, forgot about the system property. Is there anyway in code to detect that Log4J has not initialised properly (i.e could not locate a config file)? Would be nice to have a final strategy just prior to main Chainsaw startup to provide a JFileChooser to allow the user to go find it and reattempt initialization. Lastly, when I've got the code in a reasonable first state, should I post Patches into Bugzilla for review, or direct to the list? cheers, Paul Smith --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
