[
https://issues.apache.org/jira/browse/SLING-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776480#action_12776480
]
Ian Boston commented on SLING-1181:
-----------------------------------
x43543-2:tmp ieb$ curl
http://localhost:8080/apps/someResourceType/bundleresource.esp
This is the node at <%=currentNode.path%>x43543-2:tmp ieb$
x43543-2:tmp ieb$
So yes a direct url to the resource resolves, but it does not appear on the
list, indicating that registration is not complete.
}x43543-2:tmp ieb$ curl http://localhost:8080/apps.tidy.5.json
{
"jcr:created": "Wed Nov 11 2009 14:00:23 GMT+0000",
"jcr:primaryType": "sling:Folder",
"sling": {
"jcr:created": "Wed Nov 11 2009 14:00:23 GMT+0000",
"jcr:primaryType": "sling:Folder",
............
}
},
"someResourceType": {
},
}
>From this it looks like the BundleResourceProvider is partially registered and
>has not registered the full path to the resource, or is not listing its
>children (the resolution of ServletResources relies on the listing of children
>at each layer)
This is confirmed by browsing with a webdav client that does not see
someResourceType or bundleresource.esp
I think I have a better idea where the problem is now.
> Scripts loaded by Bundle Resource Provider are not found in script resolution
> -----------------------------------------------------------------------------
>
> Key: SLING-1181
> URL: https://issues.apache.org/jira/browse/SLING-1181
> Project: Sling
> Issue Type: Bug
> Reporter: Vidar S. Ramdal
> Assignee: Ian Boston
> Priority: Critical
> Attachments: SLING-1181-test-bundle-source-and-jar.zip
>
>
> When a script file is loaded as a bundle resource (using
> Sling-Bundle-Resources directive), it is not picked up during script
> resolution.
> The bundle resource IS listed at /system/console/bundleresources, and the
> script source is available at its URL under /apps.
> I can reproduce this problem using the latest trunk build (rev #834413), but
> not in builds prior to rev#825679. I will try to narrow it down, to find the
> actual change causing this.
> To reproduce:
> 1. Run a fresh Sling build
> 2. Upload a bundle with a
> <Sling-Bundle-Resources>/apps</Sling-Bundle-Resources> directive, containing
> a file at /apps/someResourceType/bundleresource.esp. The script file could
> contain the code:
> "BundleResource script, <%=currentNode.path%>"
> 3. Using WebDAV, create a script at /apps/someResourceType/webdav.esp. The
> script file could contain the code:
> "WebDAV-uploaded script, <%=currentNode.path%>"
> 4. Create a node /test, with sling:resourceType=someResourceType
> 5. Browse to http://localhost:8080/apps/someResourceType/bundleresource.esp,
> and assert that the source code of the script file is displayed
> 6. Browse to http://localhost:8080/system/console/bundleresources, and assert
> that the /apps resource is listed
> 7. Browse to http://localhost:8080/test.webdav, and assert that the
> WebDAV-uploaded script is used to render the node (displaying
> "WebDAV-uploaded script, /test")
> 8. Browse to http://localhost:8080/test.bundleresource
> Expected result:
> - The bundleresource-provided script is used to render the node, displaying
> "BundleResource script, /test"
> Actual result:
> - 403 Forbidden
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
