[ https://issues.apache.org/jira/browse/SLING-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020804#comment-16020804 ]
Andrei Dulvac commented on SLING-6868: -------------------------------------- [~cziegeler], the two sightly resource types would work with the Sing-Bundle-Resources header, but I'm not sure the [OOTB types|https://github.com/apache/sling/blob/trunk/contrib/extensions/hapi/core/src/main/resources/SLING-INF/libs/sling/hapi/types.json] would. Am I missing something? Is there a way to create nodes with arbitrary primary types and properties? > Initial content should use more specific path or be migrated to bundle > resources > -------------------------------------------------------------------------------- > > Key: SLING-6868 > URL: https://issues.apache.org/jira/browse/SLING-6868 > Project: Sling > Issue Type: Bug > Components: HApi > Affects Versions: HApi 1.0.0 > Reporter: Carsten Ziegeler > Assignee: Andrei Dulvac > Fix For: HApi 1.0.2, HApi 2.0.0 > > > Currently the initial content in the hapi bundle does not specify a path, > which means it is using "/". > When applied at the wrong time, it potentially could wipe the whole > repository. In addition initial content should always be specified with the > most specific path (the tree the bundle is owning) > So the path is something like /libs/sling/hapi > or even > /libs/sling/hapi/components -- This message was sent by Atlassian JIRA (v6.3.15#6346)