Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: exclude-result-prefixes not working on server side transformation

From: Martin Honnen <mahotrash@-----.-->
To: NULL
Date: 12/8/2004 2:11:00 PM

Keith Chadwick wrote:

> Have a server side transformation that transforms data returns via 
> SqlXMLCommand.  But the server side transform is not removing the 
> sql namespace.  Code is as follows


> sSQL = "<ROOT xmlns:sql=""urn:schemas-microsoft-com:xml-sql"">"
> sSQL += "<contacts>"
> sSQL += "<sql:query>Select * from contacts for xml auto</sql:query>"

> xmlstr = "<?xml version='1.0'?>"
> xmlstr += "<xsl:stylesheet version=""1.0""  
> xmlns:xsl=""http://www.w3.org/1999/XSL/Transform"" 
> xmlns:sql=""urn:schemas-microsoft-com:xml-sql"" "
> xmlstr += " exclude-result-prefixes=""sql"" >"


> xmlstr += "<xsl:copy-of select="".""/>"

You are copying nodes with the namespace, if you want to transform an 
element in a namespace to an unqualified element then you need to do 
that explictly e.g.
   <xsl:template match="sql:query">
     <xsl:element name="{local-name()}">
       <xsl:apply-templates />
     </xsl:element>
   </xsl:template>

-- 

	Martin Honnen
	http://JavaScript.FAQTs.com/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent