You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by sd...@apache.org on 2007/08/07 08:49:25 UTC
svn commit: r563405 -
/logging/log4j/branches/v1_2-branch/src/main/resources/org/apache/log4j/xml/logger.dtd
Author: sdeboy
Date: Mon Aug 6 23:49:24 2007
New Revision: 563405
URL: http://svn.apache.org/viewvc?view=rev&rev=563405
Log:
- added logger.dtd to support processing of java.util.logging dtd-formatted events
- added locationInfo support to multicastappender
(note: no support for MDC or event properties in XMLLayout/1.2 log4j.dtd, so application/hostname properties won't be sent for udp/multicastappender)
- updated logfilepatternreceiver to support tailing over VFS (VFSlogfilepatternreceiver commit will follow shortly)
tested udpappender/receiver, socketappender/receiver, logfilepatternreceiver, xmlsocketreceiver receiving events from java.util.logging sockethandler
Added:
logging/log4j/branches/v1_2-branch/src/main/resources/org/apache/log4j/xml/logger.dtd
Added: logging/log4j/branches/v1_2-branch/src/main/resources/org/apache/log4j/xml/logger.dtd
URL: http://svn.apache.org/viewvc/logging/log4j/branches/v1_2-branch/src/main/resources/org/apache/log4j/xml/logger.dtd?view=auto&rev=563405
==============================================================================
--- logging/log4j/branches/v1_2-branch/src/main/resources/org/apache/log4j/xml/logger.dtd (added)
+++ logging/log4j/branches/v1_2-branch/src/main/resources/org/apache/log4j/xml/logger.dtd Mon Aug 6 23:49:24 2007
@@ -0,0 +1,68 @@
+<!-- DTD used by the java.util.logging.XMLFormatter -->
+<!-- This provides an XML formatted log message. -->
+
+<!-- The document type is "log" which consists of a sequence
+of record elements -->
+<!ELEMENT log (record*)>
+
+<!-- Each logging call is described by a record element. -->
+<!ELEMENT record (date, millis, sequence, logger?, level,
+class?, method?, thread?, message, key?, catalog?, param*, exception?)>
+
+<!-- Date and time when LogRecord was created in ISO 8601 format -->
+<!ELEMENT date (#PCDATA)>
+
+<!-- Time when LogRecord was created in milliseconds since
+midnight January 1st, 1970, UTC. -->
+<!ELEMENT millis (#PCDATA)>
+
+<!-- Unique sequence number within source VM. -->
+<!ELEMENT sequence (#PCDATA)>
+
+<!-- Name of source Logger object. -->
+<!ELEMENT logger (#PCDATA)>
+
+<!-- Logging level, may be either one of the constant
+names from java.util.logging.Constants (such as "SEVERE"
+or "WARNING") or an integer value such as "20". -->
+<!ELEMENT level (#PCDATA)>
+
+<!-- Fully qualified name of class that issued
+logging call, e.g. "javax.marsupial.Wombat". -->
+<!ELEMENT class (#PCDATA)>
+
+<!-- Name of method that issued logging call.
+It may be either an unqualified method name such as
+"fred" or it may include argument type information
+in parenthesis, for example "fred(int,String)". -->
+<!ELEMENT method (#PCDATA)>
+
+<!-- Integer thread ID. -->
+<!ELEMENT thread (#PCDATA)>
+
+<!-- The message element contains the text string of a log message. -->
+<!ELEMENT message (#PCDATA)>
+
+<!-- If the message string was localized, the key element provides
+the original localization message key. -->
+<!ELEMENT key (#PCDATA)>
+
+<!-- If the message string was localized, the catalog element provides
+the logger's localization resource bundle name. -->
+<!ELEMENT catalog (#PCDATA)>
+
+<!-- If the message string was localized, each of the param elements
+provides the String value (obtained using Object.toString())
+of the corresponding LogRecord parameter. -->
+<!ELEMENT param (#PCDATA)>
+
+<!-- An exception consists of an optional message string followed
+by a series of StackFrames. Exception elements are used
+for Java exceptions and other java Throwables. -->
+<!ELEMENT exception (message?, frame+)>
+
+<!-- A frame describes one line in a Throwable backtrace. -->
+<!ELEMENT frame (class, method, line?)>
+
+<!-- an integer line number within a class's source file. -->
+<!ELEMENT line (#PCDATA)>
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Why place logger.dtd in log4j.jar (was Re: svn commit: r563405 - /logging/log4j/branches/v1_2-branch/src/main/resources/org/apache/log4j/xml/logger.dtd)
Posted by Curt Arnold <ca...@apache.org>.
On Aug 21, 2007, at 7:12 PM, Scott Deboy wrote:
> I thought it would be a good idea to put it in the same location as
> log4j.dtd.
>
> Scott
>
The file looks identical to http://java.sun.com/dtd/logger.dtd, but
with the copyright notice removed. Is it essential to do a
validating parse of the JUL log files? If not, then we could just
have the entity resolver return an zero-byte stream on a request for
logger.dtd and everything would be fine.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
RE: Why place logger.dtd in log4j.jar (was Re: svn commit: r563405 - /logging/log4j/branches/v1_2-branch/src/main/resources/org/apache/log4j/xml/logger.dtd)
Posted by Scott Deboy <sd...@comotivsystems.com>.
I thought it would be a good idea to put it in the same location as
log4j.dtd.
Scott
-----Original Message-----
From: Curt Arnold [mailto:carnold@apache.org]
Sent: Tuesday, August 21, 2007 4:56 PM
To: Log4J Developers List
Subject: Why place logger.dtd in log4j.jar (was Re: svn commit: r563405
-
/logging/log4j/branches/v1_2-branch/src/main/resources/org/apache/log4j/
xml/logger.dtd)
On Aug 8, 2007, at 11:41 AM, Curt Arnold wrote:
>
> On Aug 7, 2007, at 1:49 AM, sdeboy@apache.org wrote:
>
>> Author: sdeboy
>> Date: Mon Aug 6 23:49:24 2007
>> New Revision: 563405
>>
>> URL: http://svn.apache.org/viewvc?view=rev&rev=563405
>> Log:
>> - added logger.dtd to support processing of java.util.logging dtd-
>> formatted events
>> - added locationInfo support to multicastappender
>> (note: no support for MDC or event properties in XMLLayout/1.2
>> log4j.dtd, so application/hostname properties won't be sent for
>> udp/multicastappender)
>>
>> - updated logfilepatternreceiver to support tailing over VFS
>> (VFSlogfilepatternreceiver commit will follow shortly)
>>
>> tested udpappender/receiver, socketappender/receiver,
>> logfilepatternreceiver, xmlsocketreceiver receiving events from
>> java.util.logging sockethandler
>>
>> Added:
>> logging/log4j/branches/v1_2-branch/src/main/resources/org/
>> apache/log4j/xml/logger.dtd
>
> I don't see why logger.dtd needs to be added the log4j itself. I
> could find no references to it within log4j, though it is
> referenced in receivers. It would seem like placing the DTD within
> the receivers jar would be preferable.
>
Still waiting for a response. Placing it in log4j.jar seems to be
the wrong place.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Why place logger.dtd in log4j.jar (was Re: svn commit: r563405 - /logging/log4j/branches/v1_2-branch/src/main/resources/org/apache/log4j/xml/logger.dtd)
Posted by Curt Arnold <ca...@apache.org>.
On Aug 8, 2007, at 11:41 AM, Curt Arnold wrote:
>
> On Aug 7, 2007, at 1:49 AM, sdeboy@apache.org wrote:
>
>> Author: sdeboy
>> Date: Mon Aug 6 23:49:24 2007
>> New Revision: 563405
>>
>> URL: http://svn.apache.org/viewvc?view=rev&rev=563405
>> Log:
>> - added logger.dtd to support processing of java.util.logging dtd-
>> formatted events
>> - added locationInfo support to multicastappender
>> (note: no support for MDC or event properties in XMLLayout/1.2
>> log4j.dtd, so application/hostname properties won't be sent for
>> udp/multicastappender)
>>
>> - updated logfilepatternreceiver to support tailing over VFS
>> (VFSlogfilepatternreceiver commit will follow shortly)
>>
>> tested udpappender/receiver, socketappender/receiver,
>> logfilepatternreceiver, xmlsocketreceiver receiving events from
>> java.util.logging sockethandler
>>
>> Added:
>> logging/log4j/branches/v1_2-branch/src/main/resources/org/
>> apache/log4j/xml/logger.dtd
>
> I don't see why logger.dtd needs to be added the log4j itself. I
> could find no references to it within log4j, though it is
> referenced in receivers. It would seem like placing the DTD within
> the receivers jar would be preferable.
>
Still waiting for a response. Placing it in log4j.jar seems to be
the wrong place.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r563405 - /logging/log4j/branches/v1_2-branch/src/main/resources/org/apache/log4j/xml/logger.dtd
Posted by Curt Arnold <ca...@apache.org>.
On Aug 7, 2007, at 1:49 AM, sdeboy@apache.org wrote:
> Author: sdeboy
> Date: Mon Aug 6 23:49:24 2007
> New Revision: 563405
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=563405
> Log:
> - added logger.dtd to support processing of java.util.logging dtd-
> formatted events
> - added locationInfo support to multicastappender
> (note: no support for MDC or event properties in XMLLayout/1.2
> log4j.dtd, so application/hostname properties won't be sent for udp/
> multicastappender)
>
> - updated logfilepatternreceiver to support tailing over VFS
> (VFSlogfilepatternreceiver commit will follow shortly)
>
> tested udpappender/receiver, socketappender/receiver,
> logfilepatternreceiver, xmlsocketreceiver receiving events from
> java.util.logging sockethandler
>
> Added:
> logging/log4j/branches/v1_2-branch/src/main/resources/org/
> apache/log4j/xml/logger.dtd
I don't see why logger.dtd needs to be added the log4j itself. I
could find no references to it within log4j, though it is referenced
in receivers. It would seem like placing the DTD within the
receivers jar would be preferable.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org