XSLT 1.0 Get Current DateTime

Playing with DateTime is not possible with XSLT 1.0 alone .. In a similar situations I took help of scripting .. (C#)

Sample XML:

<?xml version="1.0" encoding="utf-8"?><root>  <Apple>2011-12-01T16:33:33Z</Apple></root>

Sample XSLT:

<?xml version="1.0" encoding="utf-8"?><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"    xmlns:msxsl="urn:schemas-microsoft-com:xslt" exclude-result-prefixes="msxsl" xmlns:cs="urn:cs">  <xsl:output method="xml" indent="yes"/>  <msxsl:script language="C#" implements-prefix="cs">    <![CDATA[      public string datenow()     {        return(DateTime.Now.ToString("yyyy'-'MM'-'dd'T'HH':'mm':'ss'Z'"));     }     ]]>    </msxsl:script>      <xsl:template match="@* | node()">        <xsl:copy>            <xsl:apply-templates select="@* | node()"/>        </xsl:copy>    </xsl:template>    <xsl:template match="Apple">      <xsl:copy>      <xsl:value-of select="cs:datenow()"/>      </xsl:copy>    </xsl:template></xsl:stylesheet>

Resulting Output:

<?xml version="1.0" encoding="utf-8"?><root>  <Apple>2012-02-22T18:03:12Z</Apple></root>

The script may reside in a same file (like I have it in my sample XSLT code) or if the code triggering XSLTransformation is C# then move the same code in the calling place :)

It's better to pass current datetime from your XML engine. Declare <xsl:param name="current-datetime"/> in your xsl:stylesheet, and pass the value from processor.

You'll better pass the current data as an input / xsl:param to the template.

The XSLT aims to be purely functional language; that is, all templates / functions should conform to e.g. the following condition: If a pure function is called with parameters that cause no side-effects, the result is constant with respect to that parameter list (sometimes called referential transparency), i.e. if the pure function is again called with the same parameters, the same result will be returned (this can enable caching optimizations such as memoization).

Although there are workarounds on this (as InfantPro'Aravind' pointed out), it is not recommended to do such things; by doing it, you're ruining one of the most significant XSLT benefits.