Hi,

In the context of [1] and corroborated by the fact that repoinit was
released, what's your opinion about defining a new service in
o.a.s.scripting.api (implemented in o.a.s.scripting.core) that would
provide ResourceResolvers with restricted access for o.a.s.scripting.*
modules - for starters just one with read-only access to the search paths?

This service could identify the common use cases for ResourceResolver
usages in o.a.s.scripting.* and reduce potential code duplication.

Thanks,
Radu

[1] - https://issues.apache.org/jira/browse/SLING-5254

Reply via email to