This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
import / include using file: URI over windows networking
- To: xsl-list at lists dot mulberrytech dot com
- Subject: [xsl] import / include using file: URI over windows networking
- From: David Andersen - DefenseWeb Technologies <david dot andersen at defenseweb dot com>
- Date: Tue, 10 Apr 2001 17:54:49 -0700
- Reply-To: xsl-list at lists dot mulberrytech dot com
Hi,
I'm new here. I just thought I'd share some info I found when using a file:
URI to import / include templates over Windows networking (UNC descriptor).
Hopefully I can save someone else some frustration.
The syntax that works in all cases so far is <xsl:import
href="file:///\\saturn\dev\test2.xsl" />. It looks bad, but it works.
Here are the results of some tests I ran to compare the behavior of the
SAXON / MSXML command line parsers:
Can anyone test this on some other parsers?
------------------
<xsl:import href="file:/\\saturn\dev\test2.xsl" />
doesn't work in msxsl
works in saxon
------------------
<xsl:import href="file://\\saturn\dev\test2.xsl" />
works in msxsl
doesn't work in saxon
------------------
<xsl:import href="file:///\\saturn\dev\test2.xsl" />
works in both!
------------------
<xsl:import href="file:/v:\test2.xsl" />
works in both
------------------
<xsl:import href="file://v:\test2.xsl" />
works in msxsl
fails in saxon
------------------
<xsl:import href="file:///v:\test2.xsl" />
works in both
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list