Cannot compare xs:integer to xs:string - suppress error at XPath compile time

Question

I am using Saxon 9 in Java to compile XPath expressions like this:

net.sf.saxon.xpath.XPathEvaluator.compile(expression)

I am aware of the changes between XPath 1 and XPath 2, so I am not surprised that Saxon cannot evaluate expressions like position() = '1'.

However, is there a way to at least compile, not evaluate the expression?

It would be much easier and more robust to recursively detect and fix type incompatibilities like the one above in a compiled Expression object, than to rely on string operations and regex.

Firstly, you are using XPathEvaluator whereas you should be using XPathCompiler to compile. Secondly, certain things can be compiled and certain things not, there is no fix-all solution. Please specify what you are trying to compile and share your attempt(code you have written) — Frox
– Frox, Commented Mar 21 at 16:53

Michael Kay · Accepted Answer · 2025-03-21 20:23:05Z

0

No, there is no supported/tested mechanism in Saxon to invoke XPath parsing without also invoking type checking. However, it's open source code so you could work out what internal interfaces you could call to achieve this effect. The class XPathParser and its key methods like parse() are public.

answered Mar 21 at 20:23

Michael Kay

165k11 gold badges97 silver badges173 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Cannot compare xs:integer to xs:string - suppress error at XPath compile time

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related