[
http://jira.qos.ch/browse/LBCLASSIC-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11672#action_11672
]
Ceki Gulcu commented on LBCLASSIC-195:
--------------------------------------
While logback components can recursively invoke logback, this is discouraged.
However, given that recursive invocation cannot be always avoided, it is
tolerated.
See my reply to Joern dated 19th of March [1]. As I imagine it, a turbo filter
is authorized to modify/transform all LoggingEvent fields which are set at the
time when the turbo filters are invoked. At a later stage, the LoggingEvent is
locked and becomes read only.
Ideally, a turbo filter should be able to add or remove events on the fly.
However, I think the computational overhead would be quite substantial.
Anyway, I'll soon write a prototype in a new branch so that we could have
something more concrete to discuss.
[1] http://jira.qos.ch/browse/LBCLASSIC-195?focusedCommentId=11643#action_11643
> 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
>
> http://qos.ch/pipermail/logback-dev/2010-March/005290.html
--
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
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev
