Project

Profile

Help

Support #5175

Use error reporter set in Configuration in more places

Added by Radu Coravu 4 days ago. Updated 4 days ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2021-11-24
Due date:
% Done:

0%

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

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.

History

#1 Updated by Michael Kay 4 days ago

Yes, you're probably right. It gets quite difficult to rationalise this stuff.

#2 Updated by Radu Coravu 4 days 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.

#3 Updated by Michael Kay 4 days 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

#4 Updated by Radu Coravu 4 days ago

Thanks Michael.

Please register to edit this issue

Also available in: Atom PDF