Bug #4969


Invalid schema-aware SEF (Invalid alpha code)

Added by Michael Kay over 1 year ago. Updated 11 months ago.

Schema-Aware processing
Start date:
Due date:
% Done:


Estimated time:
Legacy ID:
Applies to branch:
10, trunk
Fix Committed on Branch:
10, trunk
Fixed in Maintenance Release:


Reported by email to support, with files available for download.

The failure occurs when loading a SEF file for a schema-aware stylesheet: it appears to contain a reference to an anonymous type whose name cannot be resolved.

Failure occurs in 10.5; it apparently worked in


test.xml (81 Bytes) test.xml Michael Kay, 2021-04-15 00:42
test.xsl (577 Bytes) test.xsl Michael Kay, 2021-04-15 00:42
config_run.xml (225 Bytes) config_run.xml Michael Kay, 2021-04-15 00:42
test.xsd (281 Bytes) test.xsd Michael Kay, 2021-04-15 00:42
config_compile.xml (213 Bytes) config_compile.xml Michael Kay, 2021-04-15 00:42
Actions #1

Updated by Michael Kay over 1 year ago

In the source XSLT, the variable declaration is:

                <xsl:variable as="element(test:e)" name="e">
			<xsl:copy-of select="$e" validation="strict" />

Saxon has inferred a type for the variable of element(test:e, (anonymous type)) and is trying to save this inferred type in the SEF file. But anonymous types have no reliable persistent name; certainly not one that will survive export of the schema to an SCM file followed by reloading.

Short of some kind of scheme that links the SEF to a schema (with change control to protect against it changing), I think we should be dropping the anonymous type from exported representation.

Actions #2

Updated by Michael Kay over 1 year ago

I'm wondering if we could introduce some kind of notation so that instead of

as='1NE nQ{}e cQ{}e_anonymous_type_1_at_line_5_of_test.xsd'

we output

as='1NE nQ{}e c~'

where the ~ means "the schema type corresponding to the declared type of the global element declaration Q{}e".

But the simpler and safer fix is simply to drop the schema type from the alpha code if it's anonymous. It doesn't actually make a big difference: inferred type information is useful to the compiler, but it's not used very much (if at all) at run-time.

Actions #3

Updated by Michael Kay over 1 year ago

Uploading the data files for future reference as it's clearly "foo-bar" data with no sensitivity.

Actions #4

Updated by Michael Kay over 1 year ago

  • Category set to Schema-Aware processing
  • Status changed from New to In Progress
  • Priority changed from Low to Normal

I've converted this to a JUnit test: s9apitests/TestXsltCompiler/testBug4969. It's working in 10.x but failing in 11.x for an unrelated reason:

Supplied static base URI  is not a valid URI
	at net.sf.saxon.trace.ExpressionPresenter.emitRetainedStaticContext(

caused by trying to export a stylesheet that has no known base URI. Fixed this to work like 10x - it will only fail when the static base URI is actually needed.

Actions #5

Updated by Michael Kay over 1 year ago

  • Status changed from In Progress to Resolved
  • Applies to branch 10, trunk added
  • Fix Committed on Branch 10, trunk added

Fixed on the 10.x and 11.x branches. An anonymous schema type in the inferred content type of an element or attribute is no longer output to the SEF file.

Actions #6

Updated by O'Neil Delpratt 11 months ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 10.6 added

Bug fix applied in the Saxon 10.6 maintenance release

Please register to edit this issue

Also available in: Atom PDF