Bug #2486: Using -catalog with .NET command line - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #2486

closed

Using -catalog with .NET command line

Added by Stefan Krause about 9 years ago. Updated about 9 years ago.

Status:

Closed

Priority:

Normal

Assignee:

O'Neil Delpratt

Category:

.NET API

Sprint/Milestone:

9.6.0.8

Start date:

2015-10-25

Due date:

% Done:

100%

Estimated time:

Legacy ID:

Applies to branch:

9.6

Fix Committed on Branch:

9.6

Fixed in Maintenance Release:

9.6.0.8

Platforms:

Description

The command line argument -catalog causes a crash on Saxon-HE 9.6.05 and 9.6.07 for .NET.

Transform.exe -s:sample.xml -xsl:sample.xsl -o:out.xml -catalog:catalog.xml

Ausnahmefehler: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl, saxon9ee, Version=9.6.0.7, Culture=neutral, PublicKeyToken=e1fdd002d5083fe6 not found

bei java.lang.Class.newInstance0(CallerID )

bei java.lang.Class.newInstance(CallerID )

bei net.sf.saxon.trans.DynamicLoader.getInstance(String className, ClassLoader classLoader)

bei net.sf.saxon.Configuration.makeURIResolver(String className)

bei net.sf.saxon.trans.XmlCatalogResolver.setCatalog(String catalog, Configuration config, Boolean isTracing)

bei net.sf.saxon.trans.CommandLineOptions.applyToConfiguration(Processor processor)

bei net.sf.saxon.Transform.doTransform(String[] args, String command)

bei Saxon.Cmd.DotNetTransform.Main(String[] args)

All files are valid and functional. Transformation.exe works as expected without the -catalog argument.

Related issues

Actions

Copy link

Updated by O'Neil Delpratt about 9 years ago

Status changed from New to In Progress
Assignee set to O'Neil Delpratt
Priority changed from Low to Normal
Found in version set to 9.6

Thanks for reporting the problem you found. Currently investigating the problem.

Actions

Copy link

Updated by O'Neil Delpratt about 9 years ago

Category set to .NET API

Update on bug issue:

So far I have managed to reproduce the exception. It seems that we are not invoking the class properly.

Actions

Copy link

Updated by O'Neil Delpratt about 9 years ago

Update:

This bug issue is related to the issue: #2306 which was fixed for Saxon-EE. However the correct fix was not applied to HE and PE in the method setDefaultSAXParserFactory of the DotNetPlatform class.

Actions

Copy link