Altova Mailing List Archives

Re: [xsl] FW: failure notice

From: Martin Honnen <Martin.Honnen@---.-->
To: xsl-list@-----.------------.---
Date: 3/18/2010 4:30:00 PM
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 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(''))


	Martin Honnen

XSL-List info and archive:
To unsubscribe, go to:
or e-mail: <mailto:xsl-list-unsubscribe@l...>


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.