Project

Profile

Help

Support #6385

closed

Saxon fails if catalog file does not exist

Added by Stefan Krause about 1 month ago. Updated 23 days ago.

Status:
Closed
Priority:
Low
Category:
Resolvers
Sprint/Milestone:
-
Start date:
2024-04-08
Due date:
% Done:

0%

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

Description

Saxon fails if a XML catalog file given by commend line option -catalog does not exist:

"%JAVA.EXE%" ^
    -cp "%SAXON.CLASSPATH%" ^
    net.sf.saxon.Transform ^
    -xsl:"%XSL.INPUTFILE%" ^
    -s:"%XML.INPUTFILE%" ^
    -o:"%XML.OUTPUTFILE%" ^
    -catalog:catalog.xml

results in

Transformation failed: Catalog file not found: catalog.xml

XML Catalogs V1.1 spec says

8. Resource Failures

The catalog processor is sometimes required to load a catalog entry file. This may occur at the beginning of processing, when dealing with the initial list of catalog entry files, or during subsequent processing of a nextCatalog entry or one of the delegate entries.

If the processor attempts to load a resource and fails (because the resource does not exist or is not reachable, for example), it must recover by ignoring the catalog entry file that failed and proceeding.

Am I missing something?


Files

failure_on_missing_catalog.xml.zip (1006 Bytes) failure_on_missing_catalog.xml.zip Stefan Krause, 2024-04-08 17:33

Please register to edit this issue

Also available in: Atom PDF