[ http://jira.qos.ch/browse/LBCLASSIC-195?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-195: -------------------------------------- You are right. I was implicitly assuming that turbo filters(and only they) could modify logging events during a brief period. I am also assuming a two phase initialization mechanism for LoggingEvent, where in the initial phase the marker, logger, level, format, prams and the throwable would be set and available for read/write. Other parameters such as the timestamp and the MDC would be not be set nor be available for read/write. After the intervention of all the installed turbo filters, LoggingEvent would be fully initialized and *locked* before being handed over to the logger-level filter and if the event passes that hurdle, handed to the appropriate appenders. Does it make sense? What use case do you imagine for allowing modifications to loggingevent later on in the event processing lifecycle?
Allow TurboFilters to modify events -----------------------------------
Key: LBCLASSIC-195 URL: http://jira.qos.ch/browse/LBCLASSIC-195 Project: logback-classic Issue Type: Improvement Components: Other Reporter: Ceki Gulcu Assignee: Ceki Gulcu Priority: Blocker
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira