> From: Dan Morrison [mailto:dman@xxxxxxxx]
> 
> However, the use of xsl:include & xsl:import rely explicitly on there
> being a 'Base URI' available to work from.
> 
> Now in my case I'm either parsing & caching my xsl long before the
> transform, or in some cases generating it from scratch. I still want to
> use xsl:include, but my xsl tree has no Base URI. > 

If you are parsing/caching/generating the xsl then you will presumably be
setting the base URI programatically. In which case, rather than injecting
the xml:base into the xsl, why not just set the SystemId on the
XSLTInputSource?

Geoff

________________________________

Geoff Dawson
geoff.dawson@xxxxxxxxxxxxxxx
 


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list