[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] document() function can't follow virtual directory path in MSXML3?


Subject: Re: [xsl] document() function can't follow virtual directory path in MSXML3?
From: Brook Ellingwood <brook@xxxxxxxxxxx>
Date: Fri, 15 Aug 2003 22:45:50 -0700

> If you are runing the transformation in the server then that path will be
> translated to "C:\virdir\home.xml", that path, given the error you reported,
> doesn't exist. The '/virdir/' path exists only on the client, i. e., when
> called by a web browser. In the server you have to use it's full path or a
> relative path (like: ../../somedir/home.xml)

Ah, that makes sense. I don't know how comfortable I am relying on a full
path to stay accurate after I finish this job (I have no control over the
hosting environment) and I haven't managed to get a relative path working
(it's a shared host, so I probably have nested virtual directories to sort
through). That's also why the "localhost" solution won't work.

The host offers no non-critical support on weekends, so I thought I'd toss
this idea out to the list while I wait to find out what the true full path
is: Is it possible (or even advisable) to run the transform, but store the
output as a variable in ASP and then pass it to the stylesheet? I'm a true
newbie at server-side scripting, and I have yet to find an example of
variable passing that I can get to work, but it seems to me that this should
at least be feasible, even if it isn't practical.

Thanks,

-- Brook


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list



Current Thread