[MAGNOLIA-3109] XPath Query error when DMS folder start with a number Created: 05/Mar/10  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.1.3, 4.2.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Benoit Segaert Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: XML File dms.019201_Test.xml    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

If the XPath does not accept this query, the DMS interface (and maybe Website interface) must forbit the creation of a node starting with a number.

How to reproduce this issue:
Upload the dms folder and files (cf attachment)

Into the Query tool:
Repository: dms
Query language: xpath
Result Item type: nt:base
Query:
019201_Test/*



 Comments   
Comment by Danilo Ghirardelli [ 06/Mar/10 ]

In the jcr specs, numbers are accepted as node names, even at the beginning. Maybe the xpath query is not ISO9075-escaped in the query tool.

Comment by Benoit Segaert [ 08/Mar/10 ]

It seems it is a Jackrabbit issue (already in version 1.5 and always in version 1.6) with XPath
We will test it with SQL path.

Comment by Jan Haderka [ 08/Mar/10 ]

http://issues.apache.org/jira/browse/JCR-579

Also keep in mind that starting JCR 2.0 (JSR-283) the XPath is deprecated as a search language.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:43:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.