Subject: Re: [xsl] document() function and error-handling From: Abel Braaksma <abel.online@xxxxxxxxx> Date: Fri, 04 Jan 2008 01:01:32 +0100 |
[.....]
-----Original Message-----
From: Scott Trenda [mailto:Scott.Trenda@xxxxxxxx] Sent: Thursday, January 03, 2008 1:02 PM
To: Nassar, Anthony
^^^^^^^^^^^^^^^
Subject: RE: [xsl] document() function and error-handling
Thanks, this actually helps a lot. A question on the subject: our
proprietary preprocessor that I'm using accesses MSXML's IXSLProcessor
in C++; do you know if the XmlResolver class is available outside of the
.NET framework? If so, I can just tell our developer who maintains the
preprocessor to force file-checking on physical paths, and to use the
same mapped-path resolution for (local) logical paths. That seems like
it'd be the better solution overall, and it'd fix some headaches of mine
in other places. :)
Again, thanks for the reply!
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] document() function and e, Nassar, Anthony | Thread | RE: [xsl] document() function and e, Scott Trenda |
Re: [xsl] xml to xml mapping - how , Jay Bryant | Date | RE: [xsl] document() function and e, Scott Trenda |
Month |