Xsl:include from classpath

Question

We are using the XML SDK for Java. We've being trying to use the <xsl:include> tag to include stylesheets with header and footer templates into other stylesheets.
I get the following error when I try to parse the stylesheet with my xml at run time on the server using the XMLProcessor class:
XSL-1002: Error while processing include XSL file (no protocol: /common.xsl)
The only way we can get the <xsl:include> to work is to use the fully qualified URL. For example:
<xsl:include href="http://localhost/common.xsl"/>.
Does anybody know how to get the processor to include using the classpath rather than making another request to the web server?
null

Answer 1

The transformer won't search the classpath, because that isn't an XSLT concept. If you want your program to control where an xsl:included document is to be loaded from, then you need to write a class that implements URIResolver and set your TransformerFactory to use it. You'd do that like this:SAXTransformerFactory factory = (SAXTransformerFactory) TransformerFactory.newInstance();
factory.setURIResolver(new BasicURIResolver());(That's an example from code that I wrote.) That class that implements URIResolver simply has to take the href that it's given and do its own classpath search, like this:private static class BasicURIResolver implements URIResolver {
   * @see URIResolver#resolve(String, String)
  public Source resolve(String href, String base) throws TransformerException {
    String url = // some calculation from its parameters
    InputStream is = this.getClass().getResourceAsStream(url);
    return new StreamSource(is);
}The "resolve" method will be called for every xsl:include, and I had to do some debugging to see what actually gets passed in its parameters. If you want the regular processing to take place instead of your own classpath search then I believe you can return null.
You might want to invent your own convention, e.g. <xsl:include href="cp://myXSL.xsl"/>, to distinguish those XSLs for which you want to search the classpath.
By the way, I believe the default, if you don't specify any path information at all, is for the transformer to search in the same directory as the containing XSL.
PC&#178;