Interesting. Given that it's a pure-Java environment (as far as I
know), I'm really quite stumped why the two OSes result in different
output. I hope it isn't a slash-backslash hassle; Windows directory
separator has been a primary culprit for any amount of hassle.
Maybe it's the difference between XIncluder.resolve(Document in) and
XIncluder.resolveInPlace(Document in) ? David?
------------------------------------------------------------------------
Bob Stayton <mailto:[email protected]>
June 6, 2011 11:30 PM
Hi,
I'm not able to duplicate this problem by running xom 1.2.6 directly
in a java command line. My relative xincludes work on Windows XP
without a problem. Is XMLShell doing something?
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message ----- From: "David Priest" <[email protected]>
To: <[email protected]>
Sent: Monday, June 06, 2011 1:14 PM
Subject: [docbook-apps] XOM XInclude: relative URIs on OS X vs. Windows
------------------------------------------------------------------------
David Priest <mailto:[email protected]>
June 6, 2011 01:14 PM
I'm using XMLShell, which uses XOM, to process xincludes for a document.
It works flawlessly on OS X.
On Windows, I get
"Exception running: xinclude
nu.xom.xinclude.BadHrefAttributeException: Could not resolve relative
URI ../User_Guide/Module_Details/persistance.xml because the
xi:include element does not have a base URI."
Is there something special about Windows that it needs a base uri?
<xi:include href="../User_Guide/Module_Details/persistance.xml"
xpointer="element(/1)"/>
I have tried setting an xml:base reset (xml:base="") and tried setting
hard paths (xml:base="C:\Users\davidp\home\doc-source\One-Sheets\").
XOM is unhappy in all cases.
Any hints on what to do next? I'm quite baffled why XOM would perform
differently on OS X versus Windows.
Thanks in advance
david
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
