Bug #2351
closedValidating an XSD from command line gives a stacktrace
100%
Description
When running
net.sf.saxon.Validate xsd:test.xsd
from the command line, if test.xsd is invalid, appropriate error messages are output, followed by an inappropriate stack trace:
Saxon-EE 9.6.0.5J from Saxonica
Java version 1.6.0_27
Using license serial number V001824
Loading schema document file:/Users/mike/Desktop/temp/test.xsd
Finished loading schema document file:/Users/mike/Desktop/temp/test.xsd
Error on line 21 of test.xsd:
Element f cannot be in the substitution group of e. Type u is not validly derived from
type xs:positiveInteger
net.sf.saxon.s9api.SaxonApiException: The schema is invalid
at com.saxonica.ee.s9api.SchemaManagerImpl.load(SchemaManagerImpl.java:120)
at com.saxonica.Validate.doValidate(Validate.java:315)
at com.saxonica.Validate.main(Validate.java:56)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)
Caused by: net.sf.saxon.type.SchemaException: The schema is invalid
at com.saxonica.ee.schema.SchemaCompiler.compile(SchemaCompiler.java:498)
at com.saxonica.ee.schema.SchemaCompiler.validate(SchemaCompiler.java:527)
at com.saxonica.config.EnterpriseConfiguration.addSchemaSource(EnterpriseConfiguration.java:500)
at com.saxonica.ee.s9api.SchemaManagerImpl.load(SchemaManagerImpl.java:118)
Updated by Michael Kay over 9 years ago
- Status changed from New to Resolved
Patch committed on the 9.6 and 9.7 branches.
Updated by O'Neil Delpratt over 9 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in version set to 9.6.0.6
Bug fix applied in the Saxon 9.6.0.6 maintenance release.
Updated by O'Neil Delpratt almost 9 years ago
- Sprint/Milestone set to 9.6.0.6
- Applies to branch 9.6 added
- Fix Committed on Branch 9.6 added
- Fixed in Maintenance Release 9.6.0.6 added
Please register to edit this issue