[
https://issues.apache.org/jira/browse/OAK-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig resolved OAK-5073.
--------------------------------
Resolution: Fixed
Fixed
in trunk: http://svn.apache.org/viewvc?rev=1768446&view=rev
1.4 branch: http://svn.apache.org/viewvc?rev=1768458&view=rev
1.2 branch:http://svn.apache.org/viewvc?rev=1768456&view=rev
1.0 branch: http://svn.apache.org/viewvc?rev=1768449&view=rev
> Bug in JcrPathParser
> --------------------
>
> Key: OAK-5073
> URL: https://issues.apache.org/jira/browse/OAK-5073
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Roy Teeuwen
> Assignee: Michael Dürig
> Fix For: 1.5.13
>
> Attachments: OAK_5073.patch
>
>
> I seem to have found a bug in the
> org.apache.jackrabbit.oak.namepath.JcrPathParser, when looking up following
> property through the session, it returns me false, while the property does
> exist.
> I have debugged the code and found following results.
> A file.scss exists at /etc/shared/mixins/file.scss
> The api that I am using:
>
> session.propertyExists("/etc/shared/mixins/shared/../file.scss/jcr:content/jcr:data");
> returns false
> => PathListener elements
> ["","etc","mixins","shared","file.scss","jcr:content","jcr:data"]
>
>
> session.propertyExists("/etc/shared/mixins/something/../file.scss/jcr:content/jcr:data");
> returns true
> => PathListener elements
> ["","etc","shared","mixins","file.scss","jcr:content","jcr:data"]
>
> session.propertyExists("/etc/shared/mixins/file.scss/jcr:content/jcr:data");
> returns true
> => PathListener elements
> ["","etc","shared","mixins","file.scss","jcr:content","jcr:data"]
> So it seems that when using the same word shared to go back on a second time
> after other words in between, results in an error:
> /etc/shared/mixins/shared/../file.scss/jcr:content/jcr:data
> I tried this with other examples
> (/etc/anything/mixins/anything/../file.scss/jcr:content/jcr:data) and always
> came to the same result that the api is not working correctly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)