It isn’t too meaningful to give a template both a name and a mode. The name attribute fully identifies a template and there cannot be two templates with the same name and different modes. The mode attribute allows the same nodes to be processed more than once, using different modes. Here is a short example: … Read more
The value of the $var variable as defined in: <xsl:variable name=”var” select=”boolean(‘false’)”/> is true() This is because in XPath “false” is an ordinary string, as opposed to false(), which is the constructor for the boolean value false() The two boolean values in XPath are (note that they are constructed!): true() and false() The detail of … Read more
I think you’ve hit upon the reason for this XSLT operation: http://www.w3schools.com/xsl/el_namespace-alias.asp which leaves your mangled namespaces intact until output is generated, when the namespace transformation is done.
test=”categoryName != ”” Edit: This covers the most likely interpretation, in my opinion, of “[not] null or empty” as inferred from the question, including it’s pseudo-code and my own early experience with XSLT. I.e., “What is the equivalent of the following Java?”: // Equivalent Java, NOT XSLT !(categoryName == null || categoryName.equals(“”)) For more details … Read more