You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2007/10/17 15:26:52 UTC

[jira] Commented: (SLING-61) Rendering of references within the repository

    [ https://issues.apache.org/jira/browse/SLING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535546 ] 

Tobias Bocanegra commented on SLING-61:
---------------------------------------

i don't see why this is necessary. it just makes script execution more magic.
if you need to include a header or a footer, just include this in your script.

further, for larger sites, you would never 'copy' add the header and footer references to every page but use some sort of inheritance.

suggest to remove this.

> Rendering of references within the repository
> ---------------------------------------------
>
>                 Key: SLING-61
>                 URL: https://issues.apache.org/jira/browse/SLING-61
>             Project: Sling
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>
> If compound content is rendered (a node and its children), it would be good to provide a mechanism which references other trees in the repository.
> Example:
> Node A
>    + header
>    + footer
> Node B
>    + content
> Node C
>    + content
> When node B or C are rendered, the header and footer of node A should be rendered as well.
> A new node type sling:Reference with a path property will be introduced to allow such references:
> Node B
>    + header [sling:Reference (path = /A/header)]
>    + content
>    + footer [sling:Reference (path = /A/footer)]
> A new content and component (ReferenceContent and ReferenceComponent) will be added.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.