problem in template matching

[Bunny Singh]

Hi Friends,
I m new to this group and also to XML and aspire for the certification. I m unable to understand the outcome of this.The xml file is as under.
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="template1.xsl"?>
<source>
<source1>
<element1>element1</element1>
<element3>element3</element3>
<element2>element2</element2>
</source1>
</source>
The XSL is as under:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="source/source1/element1">
<i>
<xsl:value-of select="."/>
</i>
</xsl:template>
<xsl:template match="element3">
<i>
<xsl:value-of select="."/>
</i>
</xsl:template>
</xsl:stylesheet>
However the output is:
element1element3element2
with element1element3 in italics.
I fail to understand why "element2" appears in the output.
Thanx in advance

[Dan Drillich]

Please look at - https://coderanch.com/t/146692/po/certification/Default-processing

[Priya Venkatesan]

I guess it could be because, the default template rule is fired. The rule being

<xsl:template match="/|*">
<xsl:apply-templates/>
</xsl:template>
Hence apply-templates, executes the child node of curent node. When element3 is matched that corresponding template rule is fired. For element2, the default template rule for text() is fired.
That is why, element1 and element3 are in italics while element2 is not.
Experts please correct me if Iam wrong

[Andles Jurgen]

So, does the processor eventually get to the stage where it says " do i have templates for children of "source1", finds it has 3 - then uses the two author defined templates for element1 and element3, and finally, uses the built in rule for the third child element2?
I looked at it for ages before finally seeing something logical happening behind the scenes. I hope this is whats happening - otherwise it makes no sense to me either!!
Andles.

[Ron Newman]

The XSLT processor looks for a template matching "/". Not finding one, it applies the default rule to "/", which is to apply templates to each child. In this case, there is one child, "source".
The XSLT processor also finds no template matching
"source", so it continues recursing, looking for a template to apply to each of the children. In this case, there is one child, "source1".
The XSLT processor again finds no template matching
"/source/source1", so it continues recursing, looking for templates to apply to each of the children:
"element1", "element3", and "element2".
It finds a template matching "source/source1/element1", so it applies that template. It also find a rule matching "element3", so it next applies that template. It does NOT find a rule matching "element2", so it applies the default template, which is to just print out the element's text value.

[Bunny Singh]

Hi,
Thanx for the responses. Given under are the default templates in case a server applies an XSLT stylesheet to an XML Document. to transform to some other format.

<xsl:template name="get-nested-content">
<xsl aram name="content"/>
<xsl:choose>
<xsl:when test="$content/*">
<xsl:apply-templates
select="$content/*"/>
</xsl:when>
<xsl therwise>
"<xsl:value-of select="$content"/>"
</xsl therwise>
</xsl:choose>
</xsl:template>
<xsl:template match="@*|*|text()|processing-
instruction()">
<xsl:copy>
<xsl:apply-templates select="@*|*|text()
|processing-instruction()"/>
</xsl:copy>
</xsl:template>
what do the templates(XPATH Part) mean. What I infer of the second template is that either the child with an attribute or any child .....
when already the condition for "all children" is specified what is the need for "@*" condition specifying child with attribute.
Plz throw some light on this.
Bunny Singh

[Bunny Singh]

Also what all are the default templates in case the XML Document and the associated styleshet are both served to the client(Web Browser) directly.
Rgds,
Bunny Singh