[
https://issues.apache.org/jira/browse/NIFI-8550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess resolved NIFI-8550.
--------------------------------
Resolution: Duplicate
> <appender name="console" class="org.apache.log4j.ConsoleAppender"> <param
> name="Target" value="System.out"/>
> ----------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-8550
> URL: https://issues.apache.org/jira/browse/NIFI-8550
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Florin Gheciu
> Priority: Trivial
>
> <?xml version="1.0" encoding="UTF-8" ?>
> <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
> <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/";>
> <appender name="console" class="org.apache.log4j.ConsoleAppender">
> <param name="Target" value="System.out"/>
> <layout class="org.apache.log4j.PatternLayout">
> <param name="ConversionPattern" value="%-5p %c\{1} - %m%n"/>
> </layout>
> </appender>
> <root>
> <priority value ="debug" />
> <appender-ref ref="console" />
> </root>
> </log4j:configuration>
> h3. XML Configuration Format
> In order to better understand the more detailed examples, it is useful to
> understand the expected format for the xml configuration files. This is
> defined by the log4j.dtd which is located in the log4j distribution jar in
> the package org.apache.log4j.xml. The contents of this file will not be
> listed in its entirety, so please feel free to open/print the file yourself.
> If you are not familiar with xml dtd file formats, then you should go find a
> good book on that subject first.
> Near the beginning of the file is the following declaration:
> {noformat}
>
> <!ELEMENT log4j:configuration (renderer*, appender*,(category|logger)*,root?,
> categoryFactory?)>
> {noformat}
> This element defines the expected structure of the xml configuration file: 0
> or more renderer elements, followed by http://www.s0s.ro 0 or more
> appender elements, followed by 0 or more logger elements, followed by 0 or 1
> root element, followed by 0 or 1 categoryFactory element. If this order is
> not followed, then errors will be printed by the xml parser at the time the
> xml file is read in. Also, as a note, the "category" element is the same as
> the logger element. Prior to log4j version 1.2, loggers were known as
> category. Much of the documentation still refers to category. Just understand
> that they are the same thing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
