You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2015/03/05 11:39:38 UTC

[jira] [Updated] (SLING-3971) SlingQuery doesn't escape paths in the JCR queries

     [ https://issues.apache.org/jira/browse/SLING-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomek Rękawek updated SLING-3971:
---------------------------------
    Fix Version/s:     (was: Sling Query 3.0.0)

> SlingQuery doesn't escape paths in the JCR queries
> --------------------------------------------------
>
>                 Key: SLING-3971
>                 URL: https://issues.apache.org/jira/browse/SLING-3971
>             Project: Sling
>          Issue Type: Bug
>          Components: Sling Query
>    Affects Versions: Sling Query 2.0.0
>            Reporter: Tomek Rękawek
>            Assignee: Tomek Rękawek
>         Attachments: SLING-3971.patch
>
>
> Steps to reproduce:
> # Create a resource R which name starts with {{0}}, eg. {{0res}}
> # Create children resources
> # Execute following code:
> {code}
> $(R).find();
> {code}
> Actual result: {{find()}} doesn't return any resources.
> Expected result: {{find()}} should return resources created in step 2.
> The bug is caused by the fact that SlingQuery doesn't escape paths passed to {{ISDESCENDANTNODE([])}} operator in {{JcrQueryBuilder#getConditionString()}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)