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 2012/10/02 21:59:08 UTC
[jira] [Closed] (LOG4J2-13) Appenders, layouts, etc should support
deferred processing
[ https://issues.apache.org/jira/browse/LOG4J2-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers closed LOG4J2-13.
-----------------------------
> Appenders, layouts, etc should support deferred processing
> ----------------------------------------------------------
>
> Key: LOG4J2-13
> URL: https://issues.apache.org/jira/browse/LOG4J2-13
> Project: Log4j 2
> Issue Type: Wish
> Reporter: Curt Arnold
> Assignee: Ralph Goers
> Fix For: 2.0-beta2
>
>
> Appenders, Layouts and the like that interact with LoggingEvent should support deferred processing.
> This can be accomplished by having a distinct extract() method where the object constructs a value object containing the info needed for later processing from the LoggingEvent and other context (such as current thread, stack trace). At some later time, this value object may be rendered to complete the layout etc. This approach eliminates the need to preemptively collect information such as stack trace that may not be used or to clone the LoggingEvent to isolate the layout or appender from external changes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org