• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 369
  • Last Modified:

bug in processing XPATH with this simple regular expression?

Take this input:
<div id="ps-content">foobar</div>

and apply this XPATH 2+:
//div[matches(@id,"^s-content$")]

I tried with BaseX and it matched!  despite the fact that "^" in regex language means "the start of the string".

Why does it match?
0
lucavilla
Asked:
lucavilla
  • 7
  • 5
2 Solutions
 
Geert BormansCommented:
I can't answer why it matches

I can confirm it should not match
and using Saxon, it rightfully does not match

I suggest you report it to BaseX as a bug to look into, because a bug it is
0
 
lucavillaAuthor Commented:
Thanks for testing it with Saxon!

I now also tested it with Xidel too and it correctly doesn't match,  while it matches if I add the "p".

Do you know where is the right place to report the bug?
0
 
Geert BormansCommented:
I did not find any bugtracker tool on the site
(I was at an XML conference this weekend in London and actually was surprised not to meet any of the basex guys there, I could have asked)
anyway, you could try baseX talk
basex-talk(at)mailman.uni-konstanz(dot)de.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
lucavillaAuthor Commented:
Done, I reported the bug to that email (mailing list): https://mailman.uni-konstanz.de/pipermail/basex-talk/2013-June/005241.html

Let's see what they say...

PS: wow, an XML conference, interesting!
0
 
Geert BormansCommented:
yeah, well actually it was pretty interesting

http://xmllondon.com/
a whole weekend, me and the other nerds :-)
0
 
lucavillaAuthor Commented:
I read the program at http://xmllondon.com/programme.jsp
Really interesting!
Too bad that I'm so far... being in Italy...
0
 
lucavillaAuthor Commented:
Solved.
The cause turned out to be Windows (7) command-line related.
If I put the XPATH in a file it works correctly!
0
 
lucavillaAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for lucavilla's comment #a39268339

for the following reason:

Solution found by experimenting
0
 
Geert BormansCommented:
If you want to accept your own answer (a bit inappropriate here actually) make sure it contains a solution. 'win 7 command-line related' is too vague.

Note I confirmed it is a bug and it should not return values, that on its own is an acceptable reassurance

What did baseX reply? What exactly is the command-line related issue? How can your accepted answer help others that run in the same issue?
If you pasted the XPath in a file and it works ... it still could be a baseX issue, them doing the wrong thing with windows command lines. Still they should look into it. I can imagine that they parse out the command line the wrong way
0
 
lucavillaAuthor Commented:
According to Microsoft about NT command shell:
" all reserved shell characters not in double quotes must be escaped. These characters have special meaning to the Windows NT command shell. The reserved shell characters are:
& | ( ) < > ^
To pass reserved shell characters as part of an argument for a command, either the entire argument must be enclosed in double quotes, or the reserved character must be escaped. Prefix a reserved character with a carat (^) character to escape it."

In the command-line that I tried it likely ignored the "^" in the regular expression considering it just an escape character of the following character. This is why it always matched no matter where I put that "^".
0
 
Geert BormansCommented:
did you try adding '^^' instead of '^', should work if I read this
0
 
lucavillaAuthor Commented:
yes and it worked but it was becoming too difficult to consider the various special characters in a XPATH to escape them automatically.
Added to the possibility to reach the command-line length limit, I preferred to avoid the problem :)
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now