Actually, the XSLT 2.0 specification says that in the dynamic context for
use-when, the set of Available Documents is empty, which means that doc() or
document() ought to fail rather than calling the URIResolver. So it seems
you might be relying on a non-conformance in the Saxon implementation -
though I can't say it's one that I am motivated to remove.
Michael Kay
Saxonica
-----Original Message-----
From: Vladimir Nesterovsky [mailto:vladimir(_at_)nesterovsky-bros(_dot_)com]
Sent: 30 August 2008 10:49
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] use-when in the xsl:inlcude
Is there something I can pass to xslt for it to evaluate that
something in the use-when attribute in the xsl:inlcude, and
xsl:import?
In particular I'm using saxon in java.
I think I have found a clean way to achieve the desired effect.
I'll define an uri resolver that among others will resolve
uri like "configuration:data".
Thus I can write:
<xsl:include href="..."
use-when="document('configuration:data')/data/xs:boolean(@xxx)"/>
I guess, this approach has a virtue to be almost processor
independent.
Thanks.
--
Vladimir Nesterovsky
http://www.nesterovsky-bros.com
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--