Re: [Refdb-users] User feedback 3
Status: Beta
Brought to you by:
mhoenicka
|
From: David N. <dav...@bi...> - 2004-03-06 07:31:08
|
Hi Markus,
>Do you have the classpaths for all the Java apps handy? I'd like to
>add example classpaths for each processor to the refdbxmlrc config
>file.
>
Here we go. I'm going to include some comments and write the whole
thing as if the reader is a relative newcomer to *nix who knows just
enough to install software, create symlinks and manipulate files. Where
available, I'll indicate relevant Debian packages.
...................................................................................
In these examples, version numbers are often left out of jar file names,
eg. logkit-1.1.jar would be logkit.jar. The short form is a symlink to
the longer titled file. This can be done by the installation script or
by the user.
In example classpaths, each component is put on a separate line for
clarity. When creating your own classpath, do not use line breaks,
continuation marks ("\") or whitespace (tabs or spaces).
Instructions for xalan, saxon, saxon-xerces and fop are largely based on
Bob Stayton's "DocBook XSL: The Complete Guide", Chapter 3 (Getting the
tools working), see <http://www.sagehill.net/docbookxsl/index.html>.
xalan
requires: xalan2.jar
xalan2.jar
- Important: this is the docbook stylesheets extension version
- look for it in 'extensions' directory of docbook xsl stylesheets
- debian package: docbook-xsl
example classpath
/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/extensions/xalan2.jar
saxon
requires: saxon.jar, saxonXXX.jar, resolver.jar, (directory: user
catalogs)
saxon.jar
- debian package: lib-saxon-java
saxonXXX.jar (where 'XXX' is version number)
- docbook stylesheet saxon extension
- found in 'extensions' subdirectory of docbook xsl stylesheets
- use jar with closest match to saxon version, eg. for saxon
version 6.4.4-1 use saxon644.jar
- debian package: docbook-xsl
resolver.jar
- Apache project's catalog resolver
- debian package: xml-commons-resolver
(directory: user catalogs)
- when using catalogs, saxon needs to find a file called
'Catalog.properties' on the classpath
- include directory containing 'Catalog.properties' file
- see saxon documentation for further details
example classpath:
/usr/share/java/saxon.jar:\
/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/extensions/saxon644.jar:\
/usr/share/java/resolver.jar:\
/home/user/xml/catalogs/
saxon-xerces
requires: as per 'saxon' PLUS xercesImpl.jar
xercesImpl.jar
- Apache's Xerces XML parser
- debian package: libxerces2-java
example classpath:
/usr/share/java/saxon.jar:\
/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/extensions/saxon644.jar:\
/usr/share/java/resolver.jar:\
/usr/share/java/xercesImpl.jar:\
/home/user/xml/catalogs/
xt
requires: xt.jar, xp.jar
xt.jar
- James Clark's XSLT transformer
- debian package: libxt-java
xp.jar
- James Clark's XML parser
- debian package: none. Download from
<http://www.jclark.com/xml/xp/>
example classpath:
/usr/share/java/xt.jar:\
/usr/share/java/xp.jar
fop
requires: fop.jar, batik.jar, xercesImpl.jar, avalon-framework.jar
fop.jar
- base fop package
batik.jar
- fop support package
xercesImpl.jar
- xml parser packaged with fop
avalon-framework.jar
- fop support package
(all .jar files)
- debian package: none, all are part of fop binary distribution
- download from <http://xml.apache.org/fop/>
example classpath:
/usr/local/java/fop/build/fop.jar:\
/usr/local/java/fop/lib/batik.jar:\
/usr/local/java/fop/lib/xercesImpl-2.2.1.jar:\
/usr/local/java/fop/lib/avalon-framework-cvs-20020806.jar
jfor
requires: jfor.jar, xerces.jar, logkit.jar
jfor.jar
- jfor base package
- debian package: none. Download from
<http://sourceforge.net/projects/jfor>
xerces.jar
- Apache's xml parser
- debian package: libxerces-java
logkit.jar
- Apache application logger
- debian package: liblogkit-java
example classpath:
/usr/share/java/jfor.jar:\
/usr/share/java/xerces.jar:\
/usr/share/java/logkit.jar
...............................................................................................................
Take whatever you think appropriate.
Regards,
David.
|