RE: [xsl] xsl:include needs absolute URI for javascript transform?

Subject: RE: [xsl] xsl:include needs absolute URI for javascript transform?
From: "Robert Koberg" <rob@xxxxxxxxxx>
Date: Thu, 25 Sep 2003 13:41:35 -0700

Don't know if this will help or not, but I had a frustrating experience that
sounds similar - so HTH...

I had a similar problem using MSXML with XML Schemas that have
include/imports that GET from a linux server. After screaming and yelling at
my computer I checked the server logs and saw that MSXML (or IE) changes the
case. So if your filename is camelCased (like your myFile.xslt) and your
server is linux/unix, you may be sending myfile.xslt which does not exist on
the linux server (it has myFile.xslt - linux is case-sensitive, windows is

But if your stuff works with a full URL, then it is probably something else.
I'll post this in case someone else comes across it...


> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx [mailto:owner-xsl-
> list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Gloom Factory
> Sent: Thursday, September 25, 2003 1:03 PM
> To: XSL-List@xxxxxxxxxxxxxxxxxxxxxx
> Ok, here is a tricky one. I'm trying to use the
> xsl:include element in
> a stylesheet.
> <xsl:inlude href="myFile.xslt"/>
> This works fine if you use it directly from an xml
> file as an attached
> stylesheet. However, when I use it to do a
> transformation via "msxml"
> transformNode function I get an access denied error.
> It turns out that
> the include needs to be an absolute URI in this
> case(not doable in my
> project). setting xml:base works fine in Mozilla, but
> I don't think
> it's implimented in IE because it doesn't work.
> Any help would be great, thanks!

 XSL-List info and archive:

Current Thread