You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2014/09/29 18:59:34 UTC
[jira] [Resolved] (SLING-1778) Symlinks / Superimposing Resources
[ https://issues.apache.org/jira/browse/SLING-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert resolved SLING-1778.
-----------------------------------
Resolution: Fixed
rev. 1628219
this is now part of contrib: https://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/superimposing
basically it's the source version from https://github.com/stefanseifert/sling-superimposing with some slight modifications:
* updated to latest sling parent pom and cleaned up version numbers of dependencies
* cleaned up documentation
* changed return type of SuperimposingManager.getRegisteredProviders() to Iterator to be more implementation-neutral
> Symlinks / Superimposing Resources
> ----------------------------------
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Julian Sedding
> Assignee: Stefan Seifert
> Fix For: Superimposing Resource Provider 0.2.0
>
> Attachments: 130704_symlinks-0.0.4.patch, symlinks.patch
>
>
> I have implemented a ResourceProvider, which allows to create symlink nodes in the JCR repository. A symlink node has a sling:symlinkTarget property, which should contain a valid JCR path. JCR content from the sling:symlinkTarget path is then exposed below the symlink node.
> There is a mixin node type, sling:Symlink with a mandatory property sling:symlinkTarget and an optional property sling:overlayable. Additionally, there is a convenience node type, sling:SymlinkResource, which extends from sling:symlinkTarget and nt:unstructured.
> ResourceProvider instances are registered for existing symlinks when the bundle is started. Modifications are taken care of via JCR observation.
> To get started:
> * apply the attached patch to a trunk checkout
> * build and install the bundle
> * create a symlink node, pointing to some existing content
> * access the symlink node e.g. via a browser
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)