[
https://issues.apache.org/jira/browse/SLING-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juan Jose Vazquez Delgado resolved SLING-453.
---------------------------------------------
Resolution: Fixed
Has been fixed using the new ManifestHeader class
(https://svn.apache.org/repos/asf/incubator/sling/trunk/commons/osgi/src/main/java/org/apache/sling/commons/osgi/ManifestHeader.java).
> Initial content loading to target location
> ------------------------------------------
>
> Key: SLING-453
> URL: https://issues.apache.org/jira/browse/SLING-453
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> 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.
