Project

Profile

Help

Bug #2486

closed

Using -catalog with .NET command line

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

Status:
Closed
Priority:
Normal
Category:
.NET API
Sprint/Milestone:
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:
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

Related to Saxon - Bug #2306: InvalidCastException: Unable to cast object of type org.apache.xml.resolver.tools.CatalogResolver ClosedO'Neil Delpratt2015-02-02

Actions
Related to Saxon - Bug #2745: org.apache.xerces.jaxp.SAXParserFactoryImpl not found in .NETClosedO'Neil Delpratt2016-05-12

Actions

Please register to edit this issue

Also available in: Atom PDF