[
https://issues.apache.org/jira/browse/SLING-6089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542023#comment-15542023
]
Carsten Ziegeler commented on SLING-6089:
-----------------------------------------
[~chetanm] I think the best option is to use both properties, the old and the
new ones. The warning can be ignored as this is actually exactly what you want
:)
I'm personally not sure, if it is worth supporting the old whiteboard, as the
new one is now out for over a year - and I guess this could be solved with a
configuration as well:
You just use the new official properties - if someone wants to run it in an
older version, an OSGi configuration for the filter, adding the pattern
property would do the trick.
> 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)
