Hi Ceki Gülcü,
Thanks for your fast reply.
So the problem is that I'm not using the Logback but the Log4j 1.3 alpha 8 version that also has
JoranConfigurator object. (author: Curt Arnold, Ceki Gülcü)
I thought I ask you since you've written it and you more likely to reply to my message from this forum.
I'm looking at the (Log4j 1.3 alpha 8) API and don't see any LoggerContext object there.
I have at the moment this in my class:
public someConstructor(String className, String propertyFile) {
//Reads the configuration file.
if (!configFile.endsWith("xml") || configFile == ""){
throw new InvalidParameterException("Invalid XML property file.");
}
logger = org.apache.log4j.Logger.getLogger(className);
JoranConfigurator jc = new JoranConfigurator();
jc.doConfigure(configFile, LogManager.getLoggerRepository());
}
This will always work even if I pass in my config file
<blah blah blah/>
Nothing will happen, that is, no exception and no log will be printed. (written etc.)
Any other suggestions?
I know this isn't the log4j forum.....
Thanks
Gregory.
There's no such thing as LoggerContext or a method
Hello Greg,
In the documentation relative to auto configuration [1], one can read:
If the configuration file is found but is ill-formed, then logback
will detect the error condition and automatically print its internal
status on the console.
So either the documentation is wrong or logback cannot find your
configuration file. In any case, you can instruct logback to print its
internal status data with the following code:
LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory();
StatusPrinter.print(lc);
See [2] for a full example.
HTH
[1] http://logback.qos.ch/manual/configuration.html#auto_configuration
[2] http://logback.qos.ch/xref/chapter3/MyApp2.html--
Greg Flex wrote:
Hi All,
I was wondering if there is an easy way to test the validity of an XML configuration file.
Just as an example I have this now in the config file <blah blah blah>
JoranConfigurator doConfigure accepts it and no exception is thrown.
Nothing gets printed or written to a file etc. however I'd like to detect that the config file is messed up.
Any suggestions?
Thanks
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
_______________________________________________
Logback-user mailing list
Logback-user@qos.ch
http://qos.ch/mailman/listinfo/logback-user