With XPath 1.0 you will have to pass it in as a parameter, or use a proprietary extension.
XPath 2.0 you can use the current-date() function:
http://www.w3.org/TR/xpath-functions/#func-current-dateTime
Jon
"I don't regret this, but I both rue and lament it.
The identity transform as applied to your case:<xsl:template match="@*|node()">
<xsl:copy>
<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="abs">
<abstract><xsl:apply-templates/></abstract>
</xsl:template>
<xsl:template match="sct">...
Thats why I say its depends what you're doing. XML is not slow per se.
A good native XML database (eXist) will have similar speed to relational database and better in cases where you are returning highly structured data.
Accessing small flat XML files will also be quicker than accessing a...
Why you say XML is slow? It depends on what you are doing.
There are big benefits to be had working with one data format throughout an application. With relational databases a lot of time and effort is spent mapping data to objects and then mapping those objects to something else.
In terms of...
Whats the code for the GridView (declarative code). You'll need to bind one of the columns to the xpath "PublisherText/@publisher_id".
Jon
"I don't regret this, but I both rue and lament it.
<xsl:function> is an XSLT 2.0 element. It allows you to write custom xpath functions that are called from a special namespace. Microsoft are working on XSLT 2.0 support, but it will not ship even with .net 3.5.
In the mean time, you can use saxon with .net for XSLT 2.0 support -...
XML does not execute anything. There must be another program involved that parses the XML and does something.
Jon
"I don't regret this, but I both rue and lament it.
XML doesn't do anything, its just a data format. What are you doing and what do you expect to happen?
Jon
"I don't regret this, but I both rue and lament it.
What is this? Its not html, so will not work in browsers unless its being transformed. Need more information.
Jon
"I don't regret this, but I both rue and lament it.
Make sure you specify the namespaces in the XSL:/SOAP-ENV:Envelope/SOAP-ENV:Body/namesp1:get_genes_by_pathwayResponse/return/itemOr if you wanted you could just do //item, but that will search every node and can be slow for large documents.
Jon
"I don't regret this, but I both rue and lament it.
I've been using eXist for a while now and I love it. The XQuery support is excellent and it seems to be robust (I have had no problems), but I have not tried using large collections. I primary use eXist + XQuery + XSL + XForms (mozilla plugin), it takes a little while to get your head around...
What's the problem? What's the desired output? To output the attribute values you need to use AVT's:<area alt="{@title}" href="{xref/@xlink:href}" shape="rect" coords="{@coords}"/>
Jon
"I don't regret this, but I both rue and lament it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.