[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] Embedding DocBook â PDF transformation in a Java web app
On 1 Aug 2023, at 13:14, Paul Hoadley <paulh@logicsquad.net> wrote:
I'm still holding out hope... I've now got a catalog.xml mapping every .xsl, .xml, .ent, and .dtd file to its 'classpath:' URI equivalent. (Another aside: given that's a really simple string manipulation, can I make my own resolver that doesn't need the catalog.xml? What would it extend, which method would I override, and how would I provide that to Saxon's Transformer?) Anyway, now this: Error at char 9 in _expression_ in xsl:param/@select on line 18 column 57 of l10n.xsl: FODC0002 I/O error reported by XML parser processing file:///xsl/docbook-xsl-1.79.2/common/l10n.xsl. Caused by java.io.FileNotFoundException: /xsl/docbook-xsl-1.79.2/common/l10n.xsl (No such file or directory) at parameter local.l10n.xml on line 18 column 57 of l10n.xsl: invoked by global parameter local.l10n.xml at file:///xsl/docbook-xsl-1.79.2/common/l10n.xsl#18 Where that line involves a call to document(''): <xsl:param name="local.l10n.xml" select="document('')"/> Looks like it's insisting on load itself from a file, and then (obviously) can't find it at that URI. How do we tell whoever is resolving calls to the document() function to use the classpath? |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]