You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Andrei Dulvac (JIRA)" <ji...@apache.org> on 2017/10/04 17:27:00 UTC

[jira] [Comment Edited] (SLING-6868) Initial content should be migrated to bundle resources

    [ https://issues.apache.org/jira/browse/SLING-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191611#comment-16191611 ] 

Andrei Dulvac edited comment on SLING-6868 at 10/4/17 5:26 PM:
---------------------------------------------------------------

[~cziegeler], after using latest bundledresource and hapi with it, the urls give me the static html component and the jsons:
http://localhost:4502/libs/sling/hapi/types/date.json works
BUT
http://localhost:4502/libs/sling/hapi/types/date.html is a 404. I was under the impression that was supposed to work. It'd be sad if it didn't :(

Looks like the problem is that nodes (in general) using the resourceType serverd by the bundle don't work. 

http://localhost:4502/libs/sling/hapi/components/type/type.html renders as a HTL template static HTML, but it can't be used as a resourceType.


was (Author: andrei.dulvac):
[~cziegeler], after using latest bundledresource and hapi with it, the urls give me the static html component and the jsons:
http://localhost:4502/libs/sling/hapi/types/date.json works
BUT
http://localhost:4502/libs/sling/hapi/types/date.html is a 404. I was under the impression that was supposed to work. It'd be sad if it didn't :(

> Initial content should 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.1.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.4.14#64029)