[
https://issues.apache.org/jira/browse/SLING-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Jose Vazquez Delgado updated SLING-453:
--------------------------------------------
Assignee: (was: Juan Jose Vazquez Delgado)
Afaik, until now the Sling-Initial-Content OSGi header could be:
<Sling-Initial-Content>bundle/content/path;overwrite:=(true|false);uninstall:=(true|false)</Sling-Initial-Content>
Because of this issue, the Sling-Initial-Content header will be:
<Sling-Initial-Content>bundle/content/path;overwrite:=(true|false);uninstall:=(true|false);path:=/root/location</Sling-Initial-Content>
IMHO, this implies the next changes in o.a.s.jcr.contenloader:
>> PathEntry: add a property rootLocation (get;set)
>> PathEntry: modify the constructor to parse the new property
>> Loader: modify "installContent" method for invoking "installFromPath" with
>> the correct parent node if "rootLocation" is not null. Otherwise, invoke
>> "installFromPath" >> with the root node.
> Initial content loading to target location
> ------------------------------------------
>
> Key: SLING-453
> URL: https://issues.apache.org/jira/browse/SLING-453
> Project: Sling
> Issue Type: Improvement
> Components: Repository
> Affects Versions: 2.0.0
> Reporter: Juan Jose Vazquez Delgado
> Priority: Minor
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> As discussed in the mailing list:
> Use case
> ======
> A Sling application needs to load content over a previous and deep hierarchy
> nodes. It could be annoying have to repeat the previous hierarchy to deploy
> the application particular content.
> Propossal
> =======
> >> Put the application content into the bundle, e.g. at SLING-INF/content
> >> Define the content in the manifest as:
> <Sling-Initial-Content>SLING-INF/content;path:=/root/location</Sling-Initial-Content>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
