[jira] [Closed] (LOG4J2-312) XML layout improvements (compact vs. pretty, namespace, namespace prefix, root element).

2014-08-27 Thread Matt Sicker (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Sicker closed LOG4J2-312. -- > XML layout improvements (compact vs. pretty, namespace, namespace prefix, > root e

[jira] [Updated] (LOG4J2-312) XML layout improvements (compact vs. pretty, namespace, namespace prefix, root element).

2013-07-18 Thread Gary Gregory (JIRA)
names, like instance variables. - Add first cut of DTD for XML layout. - Add first cut of XSD for XML layout. was: - The XML root element was “eventSet”, it is now “events”. The word “set” is misleading, because, while unlikely, it is possible that multiple log entries can carry the same

[jira] [Commented] (LOG4J2-312) XML layout improvements (compact vs. pretty, namespace, namespace prefix, root element).

2013-07-17 Thread Gary Gregory (JIRA)
lass names. - Use camelCase of attribute names, like instance variables. - Add first cut of DTD for XML layout. - Add first cut of XSD for XML layout. - Remove trailing ‘/’ at the end of the namespace. {noformat} commit -m "- Use CamelCase for element names, like class names" (12 pa

[jira] [Updated] (LOG4J2-312) XML layout improvements (compact vs. pretty, namespace, namespace prefix, root element).

2013-07-17 Thread Gary Gregory (JIRA)
, like instance variables. - Add first cut of DTD for XML layout. - Add first cut of XSD for XML layout. was: - The XML root element was “eventSet”, it is now “events”. The word “set” is misleading, because, while unlikely, it is possible that multiple log entries can carry the same timestamp

[jira] [Resolved] (LOG4J2-312) XML layout improvements (compact vs. pretty, namespace, namespace prefix, root element).

2013-07-17 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-312. - Resolution: Fixed {noformat} commit -m "[LOG4J2-312] XML layout improvements (compact vs. p

[jira] [Created] (LOG4J2-312) XML layout improvements (compact vs. pretty, namespace, namespace prefix, root element).

2013-07-17 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-312: --- Summary: XML layout improvements (compact vs. pretty, namespace, namespace prefix, root element). Key: LOG4J2-312 URL: https://issues.apache.org/jira/browse/LOG4J2-312

[jira] [Resolved] (LOG4J2-260) XML layout does not specify charset in content type

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-260. - Resolution: Fixed {noformat} commit -m "[LOG4J2-260] XML layout does not specify chars

[jira] [Created] (LOG4J2-260) XML layout does not specify charset in content type

2013-05-16 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-260: --- Summary: XML layout does not specify charset in content type Key: LOG4J2-260 URL: https://issues.apache.org/jira/browse/LOG4J2-260 Project: Log4j 2 Issue Type

[jira] [Updated] (LOG4J2-260) XML layout does not specify charset in content type

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-260: Description: XML layout does not specify charset in content type (was: HTML layout does not

[jira] [Resolved] (LOG4J2-257) XML layout ignores charset for the XML processing intruction's encoding attribute

2013-05-16 Thread Gary Gregory (JIRA)
[ https://issues.apache.org/jira/browse/LOG4J2-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory resolved LOG4J2-257. - Resolution: Fixed {noformat} commit -m "[LOG4J2-257] XML layout ignores charset for th

[jira] [Created] (LOG4J2-257) XML layout ignores charset for the XML processing intruction's encoding attribute

2013-05-16 Thread Gary Gregory (JIRA)
Gary Gregory created LOG4J2-257: --- Summary: XML layout ignores charset for the XML processing intruction's encoding attribute Key: LOG4J2-257 URL: https://issues.apache.org/jira/browse/LOG4J

Re: XML layout

2007-08-08 Thread Paul Smith
On 09/08/2007, at 3:01 AM, Curt Arnold wrote: I'd propose: 1. Adding support for properties to XMLLayout, but have it be disabled by default. Extra elements showing up in content may disrupt existing applications that consume output from XMLLayout and shouldn't just appear in a minor r

Re: XML layout

2007-08-08 Thread Curt Arnold
On Aug 7, 2007, at 5:23 PM, Paul Smith wrote: 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

RE: XML layout

2007-08-07 Thread Scott Deboy
7 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

Re: XML layout

2007-08-07 Thread Paul Smith
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

XML layout

2007-08-07 Thread Curt Arnold
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