Bug #3329
closed
XQuery version declaration is rejected XQST0031
Fix Committed on Branch:
9.8
Fixed in Maintenance Release:
Description
A query with the version declaration
xquery version '3.1'
is rejected unless the Configuration option FeatureKeys.XQUERY_VERSION is set to the value "3.1".
From 9.8, XQuery version 3.1 is the only version of the language supported. The correct behaviour is that we should ignore the version declaration and run as if 3.1 were specified. Because we only now support one version, all the machinery for configuring the XQuery processor version in the Configuration, XQueryCompiler, StaticQueryContext, and QueryModule objects is obsolescent - the relevant interfaces should all be deprecated, and calls ignored.
- Category set to XQuery Java API
- Status changed from In Progress to Resolved
- Fix Committed on Branch 9.8 added
Fixed various interfaces for setting the XQuery language version so that the interface is either deprecated or ignored, perhaps with a warning.
Also removed dead code that implemented the XQuery 1.0 rules for cyclic declarations across module boundaries; these resctrictions disappeared in XQuery 3.0.
Patched for 9.8.
I found there was a test case that expects version "2.0" to be rejected, and although I think this is questionable (see spec bug 20135) I decided to be conservative and reinstate the check that the version must be 1.0, 3.0, or 3.1.
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.8.0.3 added
Bug fix applied in the Saxon 9.8.0.3 maintenance release.
- Status changed from Resolved to Closed
Please register to edit this issue
Also available in: Atom
PDF
.