What about using an attribute for the Sling-Initial-Content header instead of having an additional header? This would allow to install content into different workspaces from one bundle (not sure if someone really needs this though....however using attributes looks a little bit nicer to me....).
So this would be something like SLING-INF/content/home;path:=/sites/sling_website;workspace:=xyz Regards Carsten Justin Edelson (JIRA) wrote > > [ > https://issues.apache.org/jira/browse/SLING-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847697#action_12847697 > ] > > Justin Edelson commented on SLING-1448: > --------------------------------------- > > done in r925533 and documented at > http://cwiki.apache.org/confluence/display/SLINGxSITE/Content+Loading+%28jcr.contentloader%29 > >> Sling-Initial-Content should be able to load content into non-default >> workspace >> ------------------------------------------------------------------------------- >> >> Key: SLING-1448 >> URL: https://issues.apache.org/jira/browse/SLING-1448 >> Project: Sling >> Issue Type: Improvement >> Components: JCR >> Reporter: Justin Edelson >> Assignee: Justin Edelson >> Fix For: JCR ContentLoader 2.0.8 >> >> > > -- Carsten Ziegeler [email protected]
