Project

Profile

Help

Bug #2486

closed

Using -catalog with .NET command line

Added by Stefan Krause over 8 years ago. Updated over 8 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
Actions #1

Updated by O'Neil Delpratt over 8 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 #2

Updated by O'Neil Delpratt over 8 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 #3

Updated by O'Neil Delpratt over 8 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 #4

Updated by O'Neil Delpratt over 8 years ago

  • Related to Bug #2306: InvalidCastException: Unable to cast object of type org.apache.xml.resolver.tools.CatalogResolver added
Actions #5

Updated by O'Neil Delpratt over 8 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

Bug fixed in the class DotNetPlatform. Patch available in the next maintenance release.

Actions #6

Updated by O'Neil Delpratt over 8 years ago

  • Status changed from Resolved to Closed
  • Fixed in version set to 9.6.0.8

Bug fix applied in the Saxon 9.6.0.8 maintenance release

Actions #7

Updated by O'Neil Delpratt over 8 years ago

  • Applies to branch 9.6 added
  • Fix Committed on Branch 9.6 added
  • Fixed in Maintenance Release 9.6.0.8 added
Actions #8

Updated by O'Neil Delpratt over 8 years ago

  • Sprint/Milestone set to 9.6.0.8
Actions #9

Updated by O'Neil Delpratt almost 8 years ago

  • Related to Bug #2745: org.apache.xerces.jaxp.SAXParserFactoryImpl not found in .NET added

Please register to edit this issue

Also available in: Atom PDF