[
https://issues.apache.org/jira/browse/SLING-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861535#action_12861535
]
Justin Edelson commented on SLING-1506:
---------------------------------------
This filter not intended to be bound to the HttpService implementation. It is
used internally to Sling. As I said before, I think this is a bug in Pax. The
Felix HttpService whiteboard only registers Filters it can deal with. Pax
simply should ignore Filters which it doesn't know how to register. It
certainly shouldn't throw an Exception.
applying this patch will result in this filter being executed twice per request:
request -> Filter -> SlingMainServlet -> Filter -> Resource
> RequestProgressTrackerLogFilter does not register with PAX WEB properly
> -----------------------------------------------------------------------
>
> Key: SLING-1506
> URL: https://issues.apache.org/jira/browse/SLING-1506
> Project: Sling
> Issue Type: Bug
> Reporter: Mike Moulton
> Priority: Minor
> Attachments: RequestProgressTrackerLogFilter.patch
>
>
> RequestProgressTrackerLogFilter will not properly register with Pax Web as
> Pax has a requirement for all Filters to either map to a servlet name or to a
> URL pattern.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
