[SLING-1181] Scripts loaded by Bundle Resource Provider are not found in script resolution

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: JCR Resource 2.0.8
• Fix Version/s: JCR Resource 2.0.8
• Component/s: JCR
• Assignee: Ian Boston
• Reporter: Vidar Skauge Ramdal
• Created: 11/Nov/09 10:08
• Updated: 17/Nov/09 20:34
• Resolved: 11/Nov/09 20:42

Description

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

Issue Links

• relates to: SLING-1156 ResourceProviderEntry uses iterators rather than maps, this becomes expensive with apps with many servlets.