Markus Karg wrote:
In my XSL stylesheet I am loading data at runtime using
document('xyz.xml')
inside of INNER.xsl, which itself is included by OUTER.xsl, which in
turn is processed by a Java application (JAXP)
When processing the stylesheet using the XALAN found in Java RE
1.6.0_17, this effectively loads from 'path-of-INNER.xsl/xyz.xml',
while
XALAN 2.7.1 effectively loads from
'current-working-dir-of-CALLING-PROCESS/xyz.xml' (not even
'path-of-OUTER.xsl/xyz.xml', which I could understand).
So my question is: Which of both processors is doing a fault here?
How
to make XALAN 2.7.1 load from either path-of-INNER.xsl or
path-of-OUTER.xsl instead from current-working-dir-of-CALLING-
PROCESS?
Looking at http://www.w3.org/TR/xslt#document a relative URI should be
resolved to the base URI of the node the "document()" call is in, if
no
second argument is passed in.
So that looks as if Xalan 2.7.1 is wrong.
As for trying to make it resolve the URI differently, try
document('xyz.xml', document(''))
The question is, whether it makes any sense to report a bug in XALAN,
since latest release is from 2007... :-(
Ok, I'll give the two-argument version a tree... :-)
Thanks!
Markus
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--