StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>You need to create a rule to match "/" or XSL will implicitly generate one for you based on a to-text conversion of the document tree.</p> <p>I would rewrite the XSL to this:</p> <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:aws="http://webservices.amazon.com/AWSECommerceService/2006-06-07"> <xsl:output method="html" encoding="UTF-8" omit-xml-declaration="yes"/> <xsl:template match="/"> <html> <head>...</head> <body> <table> <thead>...</thead> <tbody> <xsl:apply-templates select="//aws:Item"/> </tbody> </table> </body> </html> </xsl:template> <xsl:template match="aws:Item"> <tr> <td>...</td> </tr> </xsl:template> </xsl:stylesheet> </code></pre> <p>OR add this template to your existing xsl</p> <pre><code><xsl:template match="*|@*"> <xsl:apply-templates select="*|@*"/> </xsl:template> </code></pre> <p>Both templates would match document root ("/") which is the ONLY implicit match that XSL does. This first would make "/" map to the html tag which would create a table in which each table row maps to aws:item. The second would match all nodes (and attributes), output nothing, and then attempt to match all children. The first is better if you only want to process aws:Item, the second is better if you want to process all nodes. The second may (depending on the optimization features of you xslt processor and your particular xslt document) take much longer to process.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload