[
https://issues.apache.org/jira/browse/SLING-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved SLING-9365.
-------------------------------
Resolution: Fixed
Thanks [~jsedding], the decorator turned out the to be the missing part of the
puzzle. We can now not mount resource providers if we set
servletresolver_mountProviders to false and it will decorate them back into the
tree.
> Optionally don't create resource providers for servlets
> -------------------------------------------------------
>
> Key: SLING-9365
> URL: https://issues.apache.org/jira/browse/SLING-9365
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Servlets Resolver 2.6.4
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Servlets Resolver 2.6.6
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The current ServletMounter creates a resource provider for each registered
> servlet. That works fine for a given amount of servlets but can become
> problematic for a high number of servlets as it means that on the one hand,
> the number of services is doubled and on the other hand, a lot of
> notifications are send out as well as a lot of computation has to be done by
> the resource resolver.
> As an optional remedy for these kinds of scenarios, we should allow to
> configure the mounter to not provide resource providers for servlets but only
> decorate resources into the content tree.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
