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 "Ralph Goers (JIRA)" <ji...@apache.org> on 2014/01/02 08:40:51 UTC
[jira] [Commented] (LOG4J2-417) Fix Event Level / LoggerConfig
Level table at the architecture documentation page
[ https://issues.apache.org/jira/browse/LOG4J2-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860069#comment-13860069 ]
Ralph Goers commented on LOG4J2-417:
------------------------------------
Gary, if the patch was applied why is this still open?
> Fix Event Level / LoggerConfig Level table at the architecture documentation page
> ---------------------------------------------------------------------------------
>
> Key: LOG4J2-417
> URL: https://issues.apache.org/jira/browse/LOG4J2-417
> Project: Log4j 2
> Issue Type: Question
> Components: Documentation
> Affects Versions: 2.0-beta9
> Reporter: Andreas Opitz
> Priority: Trivial
> Labels: documentation, patch
> Attachments: architecture.xml.patch
>
> Original Estimate: 0.1h
> Remaining Estimate: 0.1h
>
> Hi, as I studied the "Event Level / LoggerConfig Level table" at the architecture documentation I saw that the event level ALL will be discarded. But the event level OFF would pass for further processing.
> Is this correct?
> My first assumption was that ALL would be processed by all LoggerConfig level instead of the level OFF.
> In the case my assumption is correct I would attach a patch to the issue which would correct also a small typo.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org