[
https://issues.apache.org/jira/browse/SLING-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013426#comment-15013426
]
Stefan Egli commented on SLING-5231:
------------------------------------
the discovery use cases can be divided into two different types:
# read/write access to {{/var/discovery}} (configurable at the moment)
# read of descriptor
({{resolver.adaptTo(Session.class).getRepository().getDescriptor(..)}})
regarding configurabililty of {{/var/discovery}}: in theory that could be set
to just {{'/'}} at the moment - however, that's by no means a requirement and
we could easily restrict this config to be always under {{/var}} for example.
which means: for type 1. use cases this will probably result in a "/var
service-user" - which might be shared between discovery (SLING-5231) and
eventing (SLING-5232, SLING-5230)
> Remove getAdministrativeResourceResolver() usage from Discovery components
> --------------------------------------------------------------------------
>
> Key: SLING-5231
> URL: https://issues.apache.org/jira/browse/SLING-5231
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Discovery Impl 1.2.0, Discovery Oak 1.0.2, Discovery
> Base 1.0.2, Discovery Commons 1.0.2
> Reporter: Antonio Sanso
> Assignee: Stefan Egli
> Fix For: Discovery Commons 1.0.6, Discovery Base 1.1.2, Discovery
> Oak 1.1.2, Discovery Impl 1.2.4
>
>
> * {{org.apache.sling.discovery.base}}: 6
> * {{org.apache.sling.discovery.commons}}: 3
> * {{org.apache.sling.discovery.oak}}: 4
> total of 13 occurrences
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
