It's often best to have a pipeline of transformations, each doing one job. This
might not give the best performance, but it keeps your code simple, modular,
easy to debug, and highly reusable.
Michael Kay
Saxonica
On 5 Sep 2016, at 12:49, Rahul Singh rahulsinghindia15(_at_)gmail(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Hi,
I am using below code to remove namespace, but i want to add this XSL in my
main XSL for related output fetch. Can this possible to add in same page
means main logic to extract something as well remove namespave logic:
<xsl:template match="name">
<xsl:element name="lname">
<xsl:value-of select="/lname"/>
</xsl:element>
</xsl:template>
<xsl:template match="*">
<xsl:element name="{local-name()}">
<xsl:for-each select="@*">
<xsl:attribute name="{local-name()}">
<xsl:value-of select="."/>
</xsl:attribute>
</xsl:for-each>
<xsl:apply-templates/>
</xsl:element>
</xsl:template>
XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
EasyUnsubscribe <-list/293509> (by email <>)
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--