[
https://issues.apache.org/jira/browse/SLING-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544670#comment-15544670
]
Bertrand Delacretaz commented on SLING-6089:
--------------------------------------------
I haven't looked at your latest changes but it might be useful to have both the
Sling and non-Sling filter do the same thing (setup the tracing) but only if
the other filter hasn't done it yet. I think this might help cope with all
possible scenarios.
> Log Tracer does not work with system having new HTTP whiteboard implementation
> ------------------------------------------------------------------------------
>
> Key: SLING-6089
> URL: https://issues.apache.org/jira/browse/SLING-6089
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: Log Tracer 1.0.2
>
>
> Log Tracer does not work with Sling setups which have newer HTTP Whiteboard
> implementation (org.apache.felix.http.whiteboard:3.0.0). Currently the filter
> is registered with service property
> {noformat}
> pattern=/.*
> {noformat}
> The filter does gets used for calls to /system/console but does not get
> invoked for any calls which are handled by SlingMainServlet (as reported by
> [~bdelacretaz]
> [here|http://mail-archives.apache.org/mod_mbox/sling-dev/201609.mbox/%3CCAEWfVJ%3DWUVaoD9GOTD3WpL7PSEh9_Jk3maP2WPEWWTc7dbCftw%40mail.gmail.com%3E])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
