Michael Ludwig wrote:
Robert Koberg schrieb:
You could make a call with the document function (in a non-functional
way :) ) to a back end that uses a custom uri resolver that, when
receives a certain href, logs/writes the /real/ current-dateTime and
returns <nothing/>.
That would probably not work. I tested this the other day, just out of
curiosity, calling a script that incremented a number, and found that
the result was cached when using LibXSLT, Saxon and Xalan.
you forgot to add the generate-id + a newly created node to add to the
URI. However, the processors you mention use XSLT 1.0. To get the same
behavior in XSLT 1.0 you need to be a little bit more creative and use
the extension function exslt:node-set (or equivalent for your processor).
--~------------------------------------------------------------------
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>
--~--