[XsltView] URI base for imports is meaningless [SPR-4894]

[spring-projects-issues]

Kenny MacLeod opened SPR-4894 and commented

I've been using XsltViewResolver for the first time, and found some rather peculiar behaviour when it comes to resolving the URI base for XSL imports.

Say I have a stylesheet defined in /WEB-INF/transform.xslt and that stylesheet contains <xsl:import href="import.xslt"/> where import.xslt is contained in the same WEB-INF directory. The import fails because import.xslt cannot be found.

If I then plug in my own URIResolver and make it log the href and base arguments, the base has actually resolved as file:///D:/WEB-INF. I'd expect the base to be the webapp's WEB-INF directory on disk. This is probably because when Spring wraps my transform.xslt in a StreamSource (via ServletContextResource) and passes that Source to the TransformerFactory, it loses all context information and doesn't know the base URi of the stylesheet.

Would it be possible for XsltViewResolver to default to a sensible implementation of URIResolver, which uses the local ResourceLoader to try and locate the resource? The current behaviour would seem to be completely useless.

---

Affects: 2.0.8, 2.5.4, 2.5.5

Backported to: 2.0.9

[spring-projects-issues]

Juergen Hoeller commented

Thanks for pointing this out! We accidentally only specified the resource location part as XSLT system id there, not the full URI... I've fixed this for Spring 2.5.6.

This will be available in tonight's 2.5.6 snapshot (http://static.springframework.org/downloads/nightly/snapshot-download.php?project=SPR). Please give it a try and let me know whether it works for you now...

Juergen