You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/10/19 16:48:50 UTC
[jira] Updated: (SLING-72) SlingScriptResolver does not work
[ https://issues.apache.org/jira/browse/SLING-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-72:
-----------------------------------
Component/s: microsling
> SlingScriptResolver does not work
> ---------------------------------
>
> Key: SLING-72
> URL: https://issues.apache.org/jira/browse/SLING-72
> Project: Sling
> Issue Type: Bug
> Components: microsling
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> The new SlingScriptResolver does not work for three reasons:
> (1) It has the wrong check in the resolveScript method return null if an item expected to be a node actually is a node.
> (2) It expects nodes addressed by the script path to be either nt:file/nt:resource tuples or a structure of nodes whose primary item trail may be followed to ultimately find the property containing the script. In fact Jackrabbit WebDAV seems to create the jcr:content node of an nt:file node as a node of type nt:unstructured and thus the primary item trail breaks early.
> (3) If the request contains selectors, the script path contains slashes, which is invalid for the Node.getNodes(pattern) method, which expects direct children.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.