Paul, > > 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.
You could just check for the property and if not defined, open a JFileChooser. I don't know how much effort you want to spend detecting a bad configuration file. > 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? Post them directly to the list. -Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
