Sorry; if I'd read your posting more carefully I'd have noticed that you
weren't asking about .NET. Nonetheless, you can introduce an ISAXLocator
somewhere into the stream
(http://msdn2.microsoft.com/en-us/library/ms753775(VS.85).aspx). That
takes you deep into the bowels of MSXML and COM, though.

-----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!