Adding catalog support into Saxon

Saxon allows you to replace parser used to read XML files and XSLT stylesheets. Usually you need catalogs only for input XML files. To use Saxon with catalog files do following steps:

If you use Saxon on regular basis, you probably want to make some batch file or shell script to invoke it. If you have already path to your catalogs stored in environment variable SGML_CATALOG_FILES create something like saxon.bat on Windows:

@java -cp /path/to/saxoncatalog.jar;/path/to/saxon.jar -Dxml.catalog.files=%SGML_CATALOG_FILES% com.icl.saxon.StyleSheet -x cz.kosek.CatalogXMLReader  %1 %2 %3 %4 %5 %6 %7 %8 %9

Or if you are happy unix user:

#!/bin/sh @java -cp /path/to/saxoncatalog.jar;/path/to/saxon.jar -Dxml.catalog.files=$SGML_CATALOG_FILES com.icl.saxon.StyleSheet -x cz.kosek.CatalogXMLReader  $*

This version of catalog support uses Saxon's internal parser Ælfred. Currently it is also able to handle all encodings supported by your JVM, so there is no problem using it with some documents in national specific encodings.

Saxon is able to use user supplied parser to read XML files. This parser must implement XMLReader interface from SAX2. My solution to catalog classes uses existing implementation of this interface provided by Ælfred. I created descendant of SAXDriver class in which I changed entity resolver to resolver implemented by Java Catalog Classes.

Whole magic thing is one simple class named CatalogXMLReader.java.

// Written by Jirka Kosek, jirka@kosek.cz
// NO WARRANTY! This class is in the public domain.

package cz.kosek;

import java.io.*;
import com.icl.saxon.aelfred.SAXDriver;
import com.arbortext.catalog.Catalog;
import com.arbortext.catalog.CatalogEntityResolver;

public class CatalogXMLReader extends SAXDriver
{
  static Catalog catalog = new Catalog();
  static CatalogEntityResolver resolver = new CatalogEntityResolver();

  public CatalogXMLReader()
  {
    try
    {
      catalog.loadSystemCatalogs();
      resolver.setCatalog(catalog);
    }
    catch (IOException e)
    {
      System.err.println("Error loading catalogs: " + e.getMessage());
    }
    this.setEntityResolver(resolver);
 }
}

Due to some problems in internals of Ælfred parser I must slightly modify Norm's catalog classes to not open streams in InputSource, just to return new resolved system identifier. If you are interesed in these changes, you can e-mail me.

Saxon allows you to replace parser used to read XML files and XSLT stylesheets. Usually you need catalogs only for input XML files. To use Saxon with catalog files do following steps:

If you use Saxon on regular basis, you probably want to make some batch file or shell script to invoke it. If you have already path to your catalogs stored in environment variable SGML_CATALOG_FILES create something like saxon.bat on Windows:

@java -cp /path/to/crimson.jar;/path/to/kosek.jar;/path/to/saxon.jar -Dxml.catalog.files=%SGML_CATALOG_FILES% com.icl.saxon.StyleSheet -x cz.kosek.CatalogXMLReader  %1 %2 %3 %4 %5 %6 %7 %8 %9

Or if you are happy unix user:

#!/bin/sh
@java -cp /path/to/crimson.jar;/path/to/kosek.jar;/path/to/saxon.jar -Dxml.catalog.files=$SGML_CATALOG_FILES com.icl.saxon.StyleSheet -x cz.kosek.CatalogXMLReader  $*

As a side-effect of using Crimson parser, you can use all encodings supported by your JVM in your XML and XSLT files.

Saxon is able to use user supplied parser to read XML files. This parser must implement XMLReader interface from SAX2. My solution to catalog classes uses existing implementation of this interface by Crimson. I created descendant of Crimson XMLReader class in which I changed entity resolver to resolver implemented by Java Catalog Classes.

Whole magic thing is one simple class named CatalogXMLReader.java. In order to build it, you must have Crimson parser and above mentioned Java Catalog Classes.