[
https://issues.apache.org/jira/browse/SLING-13090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055987#comment-18055987
]
Konrad Windszus commented on SLING-13090:
-----------------------------------------
No information about the wrapped instance is exposed from any of the wrappers
at
https://github.com/apache/sling-org-apache-sling-api/tree/master/src/main/java/org/apache/sling/api/wrappers.
However introducing an additional interface like {{FilterWrapper}} exposing
something like {{getWrappedFilter()}} would have side effects (potentially
registering not only as Filter with OSGi but also as FilterWrapper). Maybe a
generic getDelegate() method can be exposed to all relevant wrappers which are
then just called to also expose information about the underlying
javax.servlet.Filter. WDYT [~rombert]?
> Filter Web Console Printer should expose additional information for
> JavaxToJakartaFilterWrapper
> -----------------------------------------------------------------------------------------------
>
> Key: SLING-13090
> URL: https://issues.apache.org/jira/browse/SLING-13090
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Reporter: Konrad Windszus
> Priority: Major
> Attachments: Screenshot 2026-02-02 at 17.57.02.png
>
>
> The Web Console printer at {{/system/console/status-slingfiler}} just exposes
> the top-level class name of each Sling fillter. That is not helpful in case
> this is a wrapper like {{JavaxToJakartaFilterWrapper}}. The wrapped class
> name should be exposed as well in order to be able to distinguish.
> !Screenshot 2026-02-02 at 17.57.02.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
