Okay, the main idea is to have some kind of references which allows to create virtual trees in a transparent way. I thought that this could be useful. :)
Let's consider an example with a page node which has a header, footer and content node. Rendering of the page node is always the same (header, content, footer). Now, with these references it's possible to reference parts of the page from a template or master page. And the page rendering does not need to know these things. So, that's the basic idea - now, there might be better/other ways to handle such things, but they are not transparent. Carsten Felix Meschberger (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/SLING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Felix Meschberger reopened SLING-61: > ------------------------------------ > > > Reopen the issue for further consideration. > > Carsten, could you please comment ? Thanks. > >> 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. > -- Carsten Ziegeler [EMAIL PROTECTED]
