Home >> All >> org >> apache >> log4j >> [ xml Javadoc ]

•

org.apache.log4j.xml.examples.* (2)

•

org.apache.log4j.xml.test.* (1)

• org.apache.log4j.xml: Javadoc index of package org.apache.log4j.xml.


Package Samples:

• org.apache.log4j.xml.test: XML based components.  
• org.apache.log4j.xml.examples

Classes:

• XMLLayout: The output of the XMLLayout consists of a series of log4j:event elements as defined in the log4j.dtd . It does not output a complete well-formed XML file. The output is designed to be included as an external entity in a separate file to form a correct XML file. For example, if abc is the name of the file where the XMLLayout ouput goes, then a well-formed XML file would be: <?xml version="1.0" ?> <!DOCTYPE log4j:eventSet SYSTEM "log4j.dtd" [<!ENTITY data SYSTEM "abc">]> <log4j:eventSet version="1.2" xmlns:log4j="http://jakarta.apache.org/log4j/">   &data; </log4j:eventSet> ...
• DOMConfigurator: Use this class to initialize the log4j environment using a DOM tree. The DTD is specified in log4j.dtd . Sometimes it is useful to see how log4j is reading configuration files. You can enable log4j internal logging by defining the log4j.debug variable on the java command line. Alternatively, set the debug attribute in the log4j:configuration element. As in <log4j:configuration debug="true" xmlns:log4j="http://jakarta.apache.org/log4j/"> ... </log4j:configuration> There are sample XML files included in the package.
• XMLSample: This example code shows how to read an XML based configuration file using a DOM parser. Sample XML files sample1.xml and sample2.xml are provided. Note that the log4j.dtd is not in the local directory. It is found by the class loader.
• Log4jEntityResolver: An org.xml.sax.EntityResolver specifically designed to return log4j.dtd which is embedded within the log4j jar file.
• ReportParserError: This class is needed for validating a log4j.dtd derived XML file.
• Transform
• DC
• XMLWatchdog
• SAXErrorHandler
• DOMTest

Home | Contact Us | Privacy Policy | Terms of Service