Problem in replacing XML namespace using XSLT

kris13 · December 18th, 2009, 05:35 AM

Hello Sam,

i really appreciate your prompt replies... Many thanks for that....

OK... i'll give my input.xml , transformation file and desired output.xml...
You please let me know how should i change my transformation file ...

Code:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
	xmlns:impl="oldNameSpace" xmlns:xsd="http://www.w3.org/2001/XMLSchema" >
	<soapenv:Body>
		<impl:requestData
			xmlns:impl="oldNameSpace">
			<xmlString ChangeDate="2008-12-18T14:47:11.773+01:00"
				IdentificationNumber="WDDKJ5GBXAF000229"
				OrderNumber="08 295 70821"
				ProductionNumber="1700158">
				<ServiceTool ExecutionTime="2008-12-18T14:47:11.773+01:00"
					UserID="kris" Version="1.1.1" />
			</xmlString>
		</impl:requestData>
	</soapenv:Body>
</soapenv:Envelope>

transformation file

Code:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

	xmlns:ser="newNameSpace" xmlns:source="oldNameSpace"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.0">
	<xsl:output method="xml" encoding="iso-8859-1" indent="yes" />


	<xsl:template match="source:*">
		<xsl:element name="{local-name()}" namespace="newNameSpace">
			<xsl:apply-templates select="@* | node()" />
		</xsl:element>
	</xsl:template>

	<xsl:template match="@*|node()">
		<xsl:copy copy-namespaces="no">
			<xsl:apply-templates select="@*|node()" />
		</xsl:copy>

	</xsl:template>

	<xsl:template match="xmlString">
		<ser:xmlString >
			<xsl:apply-templates select="@* | node()" />
		</ser:xmlString>
	</xsl:template>
</xsl:stylesheet>

desired transformed result.

Code:

<?xml version="1.0" encoding="iso-8859-1"?>
<soapenv:Envelope xmlns:ns0="newNameSpace" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:impl="oldNameSpace" xmlns:xsd="http://www.w3.org/2001/XMLSchema" >
	<soapenv:Body>
		<ns0:requestData xmlns:ns0="newNameSpace">
			<ns0:xmlString ChangeDate="2008-12-18T14:47:11.773+01:00" IdentificationNumber="WDDKJ5GBXAF000229" OrderNumber="08 295 70821" ProductionNumber="1700158">
				<ServiceTool ExecutionTime="2008-12-18T14:47:11.773+01:00" UserID="kris" Version="1.1.1"/>
			</ns0:xmlString>
		</ns0:requestData>
	</soapenv:Body>
</soapenv:Envelope>

mhkay · December 18th, 2009, 06:00 AM

I think Sam failed to spot that the inner definition of xmlns:impl is not a redundant redefinition, it is binding impl to a different namespace URI.

If you copy an element from the source then it will retain its name - that is, its "expanded name" comprising namespace URI plus local name. If you want to change its name (that is, either part of the name) you need to use xsl:element rather than xsl:copy.

The important thing is to think in terms of what are the expanded-names of the elements. Don't worry about namespace declarations - they will look after themselves if you get the names of the elements right.

samjudson · December 18th, 2009, 06:09 AM

I've ran the input you've given there against the stylesheet in your post and I get output that matches what you desired result. The prefixes might not be exactly the same, but in XML the prefix doesn't mean much - as Michael say it is the expanded name of an element that counts (the combination of the namespace and its local name).

kris13 · December 22nd, 2009, 01:22 AM

Hello Micheal & Sam,

Thanks for your replies... These solution worked out.... and i got proper result...and also thanks for informative explanation

In the solution I was getting an additional namespace attribute in result. Although that was not effecting the parsing of the response as you said..

As Micheal suggested one alternate solution also , in that he was mentioning that... these additional namespace will not come; i.e. using <xsl:element> instead of the <xsl:copy>, I tried with the following

---------------------------------------------------
Input xml
---------------------------------------------------

Code:

<?xml version="1.0" encoding="UTF-8"?>

<impl:requestData xmlns:impl="oldNameSpace">
	<impl:xmlString ChangeDate="2008-12-18T14:47:11.773+01:00"
		IdentificationNumber="WDDKJ5GBXAF000229" OrderNumber="08 295 70821"
		ProductionNumber="1700158">
		<ServiceTool ExecutionTime="2008-12-18T14:47:11.773+01:00"
			UserID="kris" Version="1.1.1" />
		<Component Version="1.1.1" />

	</impl:xmlString>
</impl:requestData>

---------------------------------------------------
desired result
---------------------------------------------------

Code:

<?xml version="1.0" encoding="UTF-8"?>

<impl:requestData xmlns:impl="newNameSpace">
	<xmlReport ChangeDate="2008-12-18T14:47:11.773+01:00"
		IdentificationNumber="WDDKJ5GBXAF000229" OrderNumber="08 295 70821"
		ProductionNumber="1700158">
		<ServiceTool ExecutionTime="2008-12-18T14:47:11.773+01:00"
			UserID="kris" Version="1.1.1" />
		<Component Version="1.1.1" />
	</xmlReport>
</impl:requestData>

---------------------------------------------------
transformation file
---------------------------------------------------

Code:

<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
	xmlns:ser="newNameSpace" xmlns:source="oldNameSpace"
	version="1.0">
	<xsl:output method="xml" encoding="iso-8859-1" indent="yes" />

	<xsl:template match="source:*">
		<xsl:element name="{local-name()}" namespace="newNameSpace">
			<xsl:copy-of select="@*|node()" >
			<xsl:apply-templates  select="@*|node()"/>
			</xsl:copy-of>
		</xsl:element>
	</xsl:template>

	<xsl:template match="source:xmlString">
		<xmlReport>
			<xsl:element name="{local-name()}" namespace="newNameSpace">
				<xsl:copy-of select="@*|node()" />
				<xsl:apply-templates select="@*|node()" />
			</xsl:element>
		</xmlReport>
	</xsl:template>
</xsl:stylesheet>

So here in result additional name space attributes; mainly for the child elements <ServiceTool> <Component> was coming while using <xsl:copy>. Although it will not effect the parsing of the document... but My XML is too large ( there are hundreds of <ServiceTool> and <Component> elements ) and these additional attributes are unnecessarily increasing the size of message.

can you please help in this....

Thanks a lot.
Krishna

mhkay · December 22nd, 2009, 04:08 AM

I don't know what the xsl:copy-of is doing in your first template - it's syntactically incorrect for xsl:copy-of to have content. And in the second template, you're creating the new element as a literal result element so you don't need xsl:element as well. Also, you seem to want the result elements to be in no namespace, so why are you putting them in a namespace called "newNamespace"?

kris13 · December 22nd, 2009, 11:39 PM

I will give you a background. I am working on Middleware (ESB) and both schmeas for both input .xml ( a consumer request ) and output.xml ( service provider ) already created and they are used since quite a long time. so i don't have the control to change these schemas ... .. and i have make them compatible to talk to each other and for that i HAVE to apply the transformation on these message

Quote:

Originally Posted by mhkay

I don't know what the xsl:copy-of is doing in your first template - it's syntactically incorrect for xsl:copy-of to have content.

I will modify that... i think my understanding of xsl:copy-of is wrong

Quote:

Originally Posted by mhkay

And in the second template, you're creating the new element as a literal result element so you don't need xsl:element as well. Also,

I am only renaming the element <impl:xmlString> to <xmlReport> and i want children of <impl:xmlString> as it is.. so i am applying a copy on this.

Quote:

Originally Posted by mhkay

you seem to want the result elements to be in no namespace, so why are you putting them in a namespace called "newNamespace"?

The very first element "<impl:requestData>" should be in a namespace and children of this should not have any namespace.. The schema is created in this way and i can't change... :-(

mhkay · December 23rd, 2009, 05:43 AM

I wasn't asking you to change the design of the XML. I was asking you why you had written the XSLT code the way you did, when it seemed to bear no relation to the output you were trying to produce.