XPATH document-function doesn't support absolute filepaths

[Vitali Gontsharuk]

Hallo!

When using the XPATH document() function to load a new XML document, we
are coming across problems, because XALAN seems to have problems with
absolute paths. XALAN always assumes that the path is relative to the
current directory. So if we e.g. are in "c:\xslt_script s" and are trying
to load an XML file from "c:\xml_files\t est.xml" it ist trying to open a
file with the following absolute path:
"c:\xslt_script s\c:\xml_files\ test.xml".
The weird thing however is that in some cases it works. Actually we
configure which XML file is to be used in a Java-Bean config-file. When
we just paste the full path to the current location of the XML file into
the config file, it works, but when we construct the path using a
place-holder (@xmlDir) which is further replaced with the actual
Dir-path, it doesn't work, although the path to the XML file - displayed
in the log of our application - is still the same.

Has someone experienced this strange behaviour too?
Any help appreciated!
Vitali Gontsharuk

[Martin Honnen]

Vitali Gontsharuk wrote:

When using the XPATH document() function to load a new XML document,
XPath 1.0 has no function named document, only XSLT 1.0 knows that function.
we
are coming across problems, because XALAN seems to have problems with
absolute paths. XALAN always assumes that the path is relative to the
current directory. So if we e.g. are in "c:\xslt_script s" and are trying
to load an XML file from "c:\xml_files\t est.xml" it ist trying to open a
file with the following absolute path:
"c:\xslt_script s\c:\xml_files\ test.xml".

I don't know what Xalan does but usually the argument is treated as a
URI reference and "c:\xml_files\t est.xml" is not a URI so you would at
least need
file:///C:/xml_files/test.xml
if you want to load from the file system.

As for resolving relative URIs, the base URI used depends on the second
argument to the document function, here is what the spec says about
that: "The URI reference may be relative. The base URI (see [3.2 Base
URI]) of the node in the second argument node-set that is first in
document order is used as the base URI for resolving the relative URI
into an absolute URI. If the second argument is omitted, then it
defaults to the node in the stylesheet that contains the expression that
includes the call to the document function."
--

Martin Honnen
http://JavaScript.FAQTs.com/

[Vitali Gontsharuk]

Martin Honnen wrote:

Vitali Gontsharuk wrote:

When using the XPATH document() function to load a new XML document,

XPath 1.0 has no function named document, only XSLT 1.0 knows that
function.

we

are coming across problems, because XALAN seems to have problems with
absolute paths. XALAN always assumes that the path is relative to the
current directory. So if we e.g. are in "c:\xslt_script s" and are
trying to load an XML file from "c:\xml_files\t est.xml" it ist trying
to open a file with the following absolute path:
"c:\xslt_script s\c:\xml_files\ test.xml".

I don't know what Xalan does but usually the argument is treated as a
URI reference and "c:\xml_files\t est.xml" is not a URI so you would at
least need
file:///C:/xml_files/test.xml
if you want to load from the file system.

As for resolving relative URIs, the base URI used depends on the
second argument to the document function, here is what the spec says
about that: "The URI reference may be relative. The base URI (see [3.2
Base URI]) of the node in the second argument node-set that is first
in document order is used as the base URI for resolving the relative
URI into an absolute URI. If the second argument is omitted, then it
defaults to the node in the stylesheet that contains the expression
that includes the call to the document function."

OK, now I've tried it in any combinations and it still doesn't work!!!
Actually I still have some problems understanding, how the function
should be called if i need to load a document whose absolute path name
is e.g. "C:\xml_files\t est.xml":
- document('file://c:/xml_files/test.xml')?
- document('file://c:\xml_files\te st.xml')?
- document('file:///c:/xml_files/test.xml')?
- document('file:///c:\xml_files\te st.xml')?

or with two parameters (according to the spec, this shouldn't be the
case, but I still tried this...):
- document('test. xml','file://c:\xml_files')?
- document('test. xml','file://c:\xml_files\') ?
- document('test. xml','file://c:/xml_files')?
- document('test. xml','file://c:/xml_files/')?
- document('file://test.xml','file ://c:/xml_files/')?
etc...
Could anyone make that function work with absolute paths???

Thanks,
Vitali

[Richard Tobin]

In article <de**********@w sc10.lrz-muenchen.de>,
Vitali Gontsharuk <go******@in.tu m.de> wrote:

Actually I still have some problems understanding, how the function
should be called if i need to load a document whose absolute path name
is e.g. "C:\xml_files\t est.xml":
This one:
- document('file:///c:/xml_files/test.xml')?

-- Richard

[Vitali Gontsharuk]

Richard Tobin wrote:

In article <de**********@w sc10.lrz-muenchen.de>,
Vitali Gontsharuk <go******@in.tu m.de> wrote:

Actually I still have some problems understanding, how the function
should be called if i need to load a document whose absolute path name
is e.g. "C:\xml_files\t est.xml":

This one:

- document('file:///c:/xml_files/test.xml')?

-- Richard

Now I figured out what the problem was: within Java Xalan had been
explicitly preconfigured with a specific directory as basepath - that's
why even absolute file paths were considered as relative.
But thanks for your answers!