Dec 22, 2010 09:53 PM|ljenner01|LINK
Through further investigation surrounding how the XSL files are being referenced, i found that there is a wrapper class which is actually copying the xsl file to a temporary directory - therefore when the xsl compiler goes to include the referenced xsl file,
it can't find it in the temporary directory because the wrapper class isn't clever enough to copy it in as well.
And then the XML error i was seeing in the browser was ligitimate because no XML was being generated at all due to the XSL compiler error - just a shame that the XSL Compiler exception was being gobbled up and not written to any logs - making this a lot
harder to solve than it needed to be!
So, the solution would be to make the wrapper class a little wiser to search through the XSL files it is copying to find any <xsl:include> or <xsl:import> statements and also copy the referenced XSL's to the temp directory...
Not sure if the benefit outweighs the performance impact of searching through the files every time though...