[
https://issues.apache.org/jira/browse/SLING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535564
]
Bertrand Delacretaz commented on SLING-61:
------------------------------------------
> Node B
> + header [sling:Reference (path = /A/header)]
> + content
> + footer [sling:Reference (path = /A/footer)]
IMHO this mixes concerns: I assume Node B is part of the *content*, yet this
header/footer business is clearly *presentation* stuff.
Having to add nodes in the content to define how it is rendered sounds terribly
wrong to me: adding a header/footer when rendering Node B is clearly a
*Component* concern.
> 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.
