Since properties are optional, I'd rather see them supported in the standard log4j.dtd without having to do anything extra.
Scott Deboy Principal Engineer COMOTIV SYSTEMS 111 SW Columbia Street Ste. 950 Portland, OR 97201 Office: 503.224.7496 Direct Line: 503.821.6482 Cell: 503.997.1367 Fax: 503.222.0185 [EMAIL PROTECTED] www.comotivsystems.com -----Original Message----- From: Paul Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 07, 2007 3:24 PM To: Log4J Developers List Subject: Re: XML layout On 08/08/2007, at 7:22 AM, Curt Arnold wrote: > The log4j 1.2 layout can produce non well formed content for some > atypical content (a message with an embedded -->, threads > containing & or >, etc). Plus it does not output MDC content > (log4j 1.3 does, but shares the other shortcomings). I've been > tempted to overhaul it but am hesitant to break code that might > have compensated for its idiosyncracies. My current thought is to > add an XsltAppender to the extras companion that uses the xslt > support added in idk 1.4. If no transform is provided, a default > transform that results in a format compatible with the current > output but done right. If you wanted some other format, you could > embed the xslt transform if you were using log4j 1.2.15 or higher > or the replacement configurator in the extras companion. Hmm, this is a tough one. If we think (and I don't know myself, I don't use XMLLayout at all) that these are really bugs, then we should feel free to address them and note in the release notes that this might be an incompatible change if people have relied on that odd behavior. Paul --------------------------------------------------------------------- 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]
