This may not be a good fit for log4* projects for a number of reasons (too heavyweight, etc). But consider that if the configuration file is xml with a known schema (or dtd, etc), then the individual implementations could use XSLT to produce a configuration file of their own specific formats at runtime. Think of it as a sort of "pre-processing" stage.
This might be an easy way to have a unified common config file format with minimal changes to each implementation. Sean Reilly Software Architect, Point2 Technologies, Inc. (306) 955-1855 [EMAIL PROTECTED] > -----Original Message----- > From: Nicko Cadell [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 18, 2003 11:49 AM > To: 'Log4J Developers List' > Subject: RE: Configuration GUI & logging.apache.org > > > FYI. Currently log4net only supports an XML config file. Also > it is not 100% > compatible with the log4j config file. Some of this is due to > different > terminology (e.g. using the attribute 'type' rather than > 'class' to specify > the dynamically loaded object types), and some due to architectural > differences. > > Nicko > > > -----Original Message----- > > From: Richard Bair [mailto:[EMAIL PROTECTED]] > > Sent: 18 February 2003 17:37 > > To: Log4J Developers List > > Subject: Configuration GUI & logging.apache.org > > > > > > Hey folks, > > > > While working on a prelim version of the configuration gui we > > noticed a > > couple of things with respect to log4j/log4perl/c++ etc > > > > 1) Apparently log4perl and others support the property style config > > files, but not xml > > 2) in log4j the properties start like 'log4j.rootlogger', > whereas perl > > is like 'log4perl.rootlogger'. > > > > We haven't exhaustively checked this out everywhere. I'd > > like to see in > > a logging.apache style project that we standardize on a config file > > format (xml is more flexible, is it not?), and also, can we change > > log4j.* and log4perl.* to log.*? > > > > I suppose there's no hope of supporting log.* in this release. > > > > Thoughts? > > Richard > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
