Actions
Bug #2404
closed
System.NullReferenceException: Object reference not set to an instance of an object
Start date:
2015-06-18
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.6
Fix Committed on Branch:
9.6
Fixed in Maintenance Release:
Platforms:
Description
The following schema validation exception was reported by user:
System.NullReferenceException: Object reference not set to an instance of an object.
at org.apache.xerces.parsers.XML11Configuration.parse(XMLInputSource xmlis)
at org.apache.xerces.parsers.XMLParser.parse(XMLInputSource xmlis)
at org.apache.xerces.parsers.AbstractSAXParser.parse(InputSource is)
at org.apache.xerces.jaxp.SAXParserImpl.JAXPSAXParser.parse(InputSource is)
at net.sf.saxon.event.Sender.sendSAXSource(SAXSource , Receiver , ParseOptions )
at net.sf.saxon.event.Sender.send(Source source, Receiver receiver, ParseOptions options)
at Saxon.Api.SchemaValidator.Run()
Updated by O'Neil Delpratt over 9 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Bug fixed and committed to subversion. The fix was in the DotNetSchemaURIResolver class which is in the Schema.cs file.
If the namespace of the schema has been seen already we try to access it in the cache. This has implications if the namespace is reused and does not match the location of the file. We set a flag to check for multiple schema imports to avoid this problem.
Updated by O'Neil Delpratt over 9 years ago
- Status changed from Resolved to Closed
- Fixed in version set to 9.6.0.7
Bug fix applied in the Saxon 9.6.0.7 maintenance release.
Updated by O'Neil Delpratt almost 9 years ago
- Applies to branch 9.6 added
- Fix Committed on Branch 9.6 added
- Fixed in Maintenance Release 9.6.0.7 added
Please register to edit this issue
Actions
.