[ http://jira.qos.ch/browse/LBCLASSIC-195?page=com.atlassian.jira.plugin.syste... ] Rü edited comment on LBCLASSIC-195 at 3/19/10 5:55 PM: ------------------------------------------------------- So there is no breaking change in 0.9.19 because of http://jira.qos.ch/browse/LBCORE-128 any more, right? But I find it irritating to have logging events changed by filters... just looking at the names of the classes would suggest that an event will never change! And even more so, a filter should just say yea or nay and not go and fiddle with the stuff it receives. Maybe I'm currently just all too spoiled by Scala, but I find it irritating. What's the use case, anyway?!? I can't see one! Performance and compatibility concerns should follow the use case, shouldn't they. was (Author: rd): So there is no breaking change in 0.9.19 because of http://jira.qos.ch/browse/LBCORE-128 any more, right? I find it irritating to have logging events changed by filters... just looking at the names of the classes would suggest that an event will never change! And even more so, a filter should just say yea or nay and not go and fiddle with the stuff it receives. Maybe I'm currently just all too spoiled by Scala, but I find it irritating. What's the use case, anyway?!? I can't see one; aside from performance and compatibility concerns.
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