[jira] Issue Comment Edited: (SLING-1778) Symlinks

["Justin Edelson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910621#action_12910621 ] 

Justin Edelson edited comment on SLING-1778 at 9/17/10 11:15 AM:
-----------------------------------------------------------------

What I'm thinking is let's say...

Node /b/bar has property text1="one" 
Node /b/baz has property text2="three" 

Node /a/foo has property text="two" 

Node /a/foo also has
sling:overlayPath = [/b/bar, /b/baz]

/a/foo.json will return

{
 'text' : 'two',
 'sling:overlayPath' : ['/b/bar', '/b/baz'],
 'text1' : 'one',
 'text2' : 'three'
}



      was (Author: justinedelson):
    What I'm thinking is let's say...

Node /b/bar has property text1="one" 
Node /b/baz has property text2="three" 

Node /a/foo has property text="two" 

Node /a/foo also has
sling:overlayPath = [/b/bar, /b/baz]

/a/foo.json will return

{
 'text' : 'two',
 'text1' : 'one',
 'text2' : 'three',
 'sling:overlayPath' : ['/b/bar', '/b/baz']
}


  
> 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: 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.