AJ Chen wrote:
I found out the following parse error is caused by the number in node path: //A/1/B If the number "1" is replaced by "*", the xpath query works: //A/*/B Is it a bug or by spec?
this is per spec. "1" is not a valid XML name, you need to escape it. see section 6.4.3.
//A/_x0031_/B will work. regards marcel
