[
https://issues.apache.org/jira/browse/SLING-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13792811#comment-13792811
]
Stefan Seifert commented on SLING-1778:
---------------------------------------
fyi - if started some more work on this feature and created a github repository
for the time being:
https://github.com/stefanseifert/sling-superimposing
i already renamed it to "superimposing resource provider" (until some comes up
with a better name, although it will be quite time consuming to rename it
again), and removed the JCR dependencies (one step missing concerning the
overlay detection). i started adding unit tests, this is not completed yet.
once this is done i will think about the possibilities to integrate the merge
possibilities from SLING-2986 into it, or into a shared piece of code. it could
be a good option to make the overlay part of this feature more flexible than it
is currently. i'm not sure where such a "shared piece of merging code" should
be placed within sling yet.
as time permits i will do some more work on it the next days.
> Symlinks
> --------
>
> Key: SLING-1778
> URL: https://issues.apache.org/jira/browse/SLING-1778
> Project: Sling
> Issue Type: New Feature
> Components: JCR
> Reporter: Julian Sedding
> 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.1#6144)
