logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-417) Fix Event Level / LoggerConfig Level table at the architecture documentation page
Date Mon, 07 Oct 2013 15:58:42 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Gregory updated LOG4J2-417:
--------------------------------

    Summary: Fix Event Level / LoggerConfig Level table at the architecture documentation
page  (was: Question regarding the Event Level / LoggerConfig Level table at the architecture
documentation page)

> 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
>   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#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message