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:46:51 UTC
[jira] Created: (SLING-72) SlingScriptResolver does not work
SlingScriptResolver does not work
---------------------------------
Key: SLING-72
URL: https://issues.apache.org/jira/browse/SLING-72
Project: Sling
Issue Type: Bug
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.
[jira] Closed: (SLING-72) SlingScriptResolver does not work
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-72.
----------------------------------
Resolution: Fixed
> Wrong node types is fixed (don't fail if it is a node as expected)
> Fix nt:file handling: Be more "stupid" and just get "jcr:content/jcr:data" property but als check
whether the node is nt:file
> Move leading relative path components from the constructed script file name to the script path
Fixed in Rev. 586538
> 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.
[jira] Updated: (SLING-72) SlingScriptResolver does not work
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (SLING-72) SlingScriptResolver does not work
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536277 ]
Bertrand Delacretaz commented on SLING-72:
------------------------------------------
I have added a note to src/main/webapp/index.html indicating that scripting is currently broken, so that people don't waste their time trying that according to the information pages.
> 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.