[
https://issues.apache.org/jira/browse/SLING-9454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447462#comment-17447462
]
Konrad Windszus commented on SLING-9454:
----------------------------------------
I think 1. and 4. is now covered in SLING-9688. Let us track 2. and 3. in
different issues. 3. should IMHO be resolved by switching from JCR Observation
to [Resource
Observation|https://sling.apache.org/documentation/the-sling-engine/resources.html#resource-observation]
to support arbitrary resource providers (not only the JCR one).
> Sling Superimposing Upgrade
> ---------------------------
>
> Key: SLING-9454
> URL: https://issues.apache.org/jira/browse/SLING-9454
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Superimposing Resource Provider 0.2.0
> Reporter: Saurabh Khare
> Priority: Major
> Labels: newbie, pull-request-available
> Fix For: Superimposing Resource Provider 0.4.0
>
>
> Sling superimposing is still relevant for particular contexts when resource
> mirroring is a necessity. SLING-1778
> This ticket is for upgrading the old sling superimposing sling extension with
> latest resource provider API and OSGI annotations.
> Following are the upgrades for the extension:
> # Upgrade Resource provider API from
> org.apache.sling.api.resource.ResourceProvider to
> org.apache.sling.spi.resource.provider.ResourceProvider
> # Upgrade to OSGi R7 annotations
> # Use of service resolver instead of administrative resource resolver
> # Upgrade for maven plugins and migration from maven-bundle-plugin to
> bnd-maven-plugin
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
