You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Aleksander Bandelj (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/03 20:25:32 UTC

[jira] [Resolved] (SLING-2262) ContentLoader loading order and content dependencies

     [ https://issues.apache.org/jira/browse/SLING-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksander Bandelj resolved SLING-2262.
---------------------------------------

    Resolution: Invalid

I need to rethink this.
                
> ContentLoader loading order and content dependencies
> ----------------------------------------------------
>
>                 Key: SLING-2262
>                 URL: https://issues.apache.org/jira/browse/SLING-2262
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>            Reporter: Aleksander Bandelj
>
> Content bundles may depend on each other. For example, it seems natural to centralize node type definitions for several content bundles in single bundle. Node type definitions from this bundle should be loaded before content from other bundles. In fact, Sakai Nakamura has recently split content bundles in this way. 
> Handling dependencies between node types in different bundles seems prohibitive, but I think loading type definitions first is better choice than completely undefined loading order. In other words, bundles with Sling-Nodetypes header should have priority.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira