Hi Mike,

Thank you for your help, and swift response.

Much appreciated.


On Tue, Jan 8, 2013 at 10:23 PM, Michael Kay <mike@saxonica.com> wrote:
The most likely explanation is that ExchangerXML is invoking Saxon without supplying a base output URI, meaning that the relative URI passed in the href attribute of xsl:result-document can't be resolved. To confirm this theory you'll have to ask the ExchangerXML developers. Or you might be able to work around it by supplying an absolute URI (starting file://...) as the href value.

Michael Kay