Support #5175
closed
Use error reporter set in Configuration in more places
100%
Description
I set an "ErrorReporterFactory" in the COnfiguration using "net.sf.saxon.Configuration.setErrorReporterFactory(Function<Configuration, ? extends ErrorReporter>)".
I use the constructor "net.sf.saxon.query.DynamicQueryContext.DynamicQueryContext(Configuration)". The dynamic query context should get the error reporter from the configuration instead of creating a standard error reporter.
I think the same when creating a static query context "net.sf.saxon.Configuration.newStaticQueryContext()", the static query context should take its initial error reporter from the Configuration.
Updated by Michael Kay almost 2 years ago
Yes, you're probably right. It gets quite difficult to rationalise this stuff.
Updated by Radu Coravu almost 2 years ago
Right, right now I set the same error reporter on 3 different objects just to make sure although they are all created based on the configuration.
Updated by Michael Kay almost 2 years ago
I have replaced creation of a StandardErrorReporter with a call on Configuration.makeErrorReporter() in the following places:
on the 10 branch:
SchemaManagerImpl constructor
Controller c'tor
StaticQueryContext c'tor and reset()
DynamicQueryContext c'tor
AbstractResourceCollection.optionsFromQueryParameters()
CompilerInfo c'tor
on the 11 branch:
SchemaManagerImpl constructor
Controller c'tor
StaticQueryContext c'tor and reset()
DynamicQueryContext c'tor
AbstractResourceCollection.optionsFromQueryParameters()
ActiveSAXSource.deliver()
CompilerInfo c'tor
Updated by Michael Kay over 1 year ago
- Category set to Diagnostics
- Status changed from New to Resolved
- Assignee set to Michael Kay
- Applies to branch 10, 11 added
- Fix Committed on Branch 10, 11 added
Marking this resolved with no further action. Note that the fixes already described will be present in 11.1 although not documented as such in the release notes.
Updated by Debbie Lockett over 1 year ago
- Fixed in Maintenance Release 11.1 added
Belatedly marking as fixed in 11.1. Waiting to close when fixed in next Saxon 10 maintenance release.
Updated by Debbie Lockett over 1 year ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 10.7 added
- Fixed in Maintenance Release deleted (
11.1)
Bug fix applied in the Saxon 10.7 maintenance release.
Updated by Debbie Lockett over 1 year ago
- Fixed in Maintenance Release 11.1 added
Please register to edit this issue
.