XSLT Question

Hi,

We are sending the below SOAP response and there is a requirement where the <Message> needs to look like                                                <Message xmlns="">

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<soapenv:Body>
		<StockAdjustmentMsg xmlns="http://www.abc-def.com/ns/schema">
			<Message>
				<Header>
					<ApiVersion>1.0.1</ApiVersion>
					<CreationTime>2014-07-18T11:30:17</CreationTime>
					<SenderId>ABCD</SenderId>
					<SenderAuth>18a51609-6ae2-4ea7-b5bd-bc8806fd</SenderAuth>
					<ReceiverId>DEF</ReceiverId>
					<MessageType>STOCK_ADJUSTMENT</MessageType>
				</Header>
				<Body>
					<MessageId>20140718113017_</MessageId>
					<StockAdjustment>
						<ProductNr>60000000006902</ProductNr>
						<Quantity>6</Quantity>
						<StockTypeTo>NEW</StockTypeTo>
						<Reason>510</Reason>
					</StockAdjustment>
				</Body>
			</Message>
		</StockAdjustmentMsg>
	</soapenv:Body>
</soapenv:Envelope>

Open in new window


Note that the XSLT needs to be general as StockAdjustmentMsg can also be different like OrderMsg etc. Also Body can repeat.

Thanks
Pradeep
Pradeep0308Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Geert BormansInformation ArchitectCommented:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    version="1.0">
    
    <xsl:template match="node()">
        <xsl:copy>
            <xsl:copy-of select="@*"/>
                <xsl:apply-templates select="node()"/>
        </xsl:copy>
    </xsl:template>
    <xsl:template match="*[local-name() = 'Message']">
        <Message>
            <xsl:copy-of select="@*"/>
            <xsl:apply-templates select="node()"/>
        </Message>
    </xsl:template>
</xsl:stylesheet>

Open in new window

0
Pradeep0308Author Commented:
Geert,

The output of the XSLT is below:

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<soapenv:Body>
		<StockAdjustmentMsg xmlns="http://www.abc-def.com/ns/schema">
			<Message xmlns="">
				<Header xmlns="http://www.abc-def.com/ns/schema">
					<ApiVersion>1.0.1</ApiVersion>
					<CreationTime>2014-07-18T11:30:17</CreationTime>
					<SenderId>ABCD</SenderId>
					<SenderAuth>18a51609-6ae2-4ea7-b5bd-bc8806fd</SenderAuth>
					<ReceiverId>DEF</ReceiverId>
					<MessageType>STOCK_ADJUSTMENT</MessageType>
				</Header>
				<Body xmlns="http://www.abc-def.com/ns/schema">
					<MessageId>20140718113017_</MessageId>
					<StockAdjustment>
						<ProductNr>60000000006902</ProductNr>
						<Quantity>6</Quantity>
						<StockTypeTo>NEW</StockTypeTo>
						<Reason>510</Reason>
					</StockAdjustment>
				</Body>
			</Message>
		</StockAdjustmentMsg>
	</soapenv:Body>
</soapenv:Envelope>

Open in new window

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body>
            <StockAdjustmentMsg xmlns="http://www.abc-def.com/ns/schema">
                  <Message xmlns="">
                        <Header xmlns="http://www.abc-def.com/ns/schema">
                              <ApiVersion>1.0.1</ApiVersion>
                              <CreationTime>2014-07-18T11:30:17</CreationTime>
                              <SenderId>ABCD</SenderId>
                              <SenderAuth>18a51609-6ae2-4ea7-b5bd-bc8806fd</SenderAuth>
                              <ReceiverId>DEF</ReceiverId>
                              <MessageType>STOCK_ADJUSTMENT</MessageType>
                        </Header>
                        <Body xmlns="http://www.abc-def.com/ns/schema">
                              <MessageId>20140718113017_</MessageId>
                              <StockAdjustment>
                                    <ProductNr>60000000006902</ProductNr>
                                    <Quantity>6</Quantity>
                                    <StockTypeTo>NEW</StockTypeTo>
                                    <Reason>510</Reason>
                              </StockAdjustment>
                        </Body>
                  </Message>
            </StockAdjustmentMsg>
      </soapenv:Body>
</soapenv:Envelope>

It is adding namespace to Header and Body also. I only need Message to look like <Message xmlns="">. Below is how I need the output to look like:

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<soapenv:Body>
		<StockAdjustmentMsg xmlns="http://www.abc-def.com/ns/schema">
			<Message xmlns="">
				<Header>
					<ApiVersion>1.0.1</ApiVersion>
					<CreationTime>2014-07-18T11:30:17</CreationTime>
					<SenderId>ABCD</SenderId>
					<SenderAuth>18a51609-6ae2-4ea7-b5bd-bc8806fd</SenderAuth>
					<ReceiverId>DEF</ReceiverId>
					<MessageType>STOCK_ADJUSTMENT</MessageType>
				</Header>
				<Body>
					<MessageId>20140718113017_</MessageId>
					<StockAdjustment>
						<ProductNr>60000000006902</ProductNr>
						<Quantity>6</Quantity>
						<StockTypeTo>NEW</StockTypeTo>
						<Reason>510</Reason>
					</StockAdjustment>
				</Body>
			</Message>
		</StockAdjustmentMsg>
	</soapenv:Body>
</soapenv:Envelope>

Open in new window

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body>
            <StockAdjustmentMsg xmlns="http://www.abc-def.com/ns/schema">
                  <Message xmlns="">
                        <Header>
                              <ApiVersion>1.0.1</ApiVersion>
                              <CreationTime>2014-07-18T11:30:17</CreationTime>
                              <SenderId>ABCD</SenderId>
                              <SenderAuth>18a51609-6ae2-4ea7-b5bd-bc8806fd</SenderAuth>
                              <ReceiverId>DEF</ReceiverId>
                              <MessageType>STOCK_ADJUSTMENT</MessageType>
                        </Header>
                        <Body>
                              <MessageId>20140718113017_</MessageId>
                              <StockAdjustment>
                                    <ProductNr>60000000006902</ProductNr>
                                    <Quantity>6</Quantity>
                                    <StockTypeTo>NEW</StockTypeTo>
                                    <Reason>510</Reason>
                              </StockAdjustment>
                        </Body>
                  </Message>
            </StockAdjustmentMsg>
      </soapenv:Body>
</soapenv:Envelope>

Thanks
Pradeep
0
Geert BormansInformation ArchitectCommented:
Actually you asked
<Message xmlns="">
which is mechanical to say that Message is NOT in the namespace of the higher up element it would inherit the default namespace from
(you are basically switching back to the null namespace for this element)

Now you ask to take out the entire Mesaage including children, to the null namespace
(note that you are making it different elements

the xmlns="" will not appear if the parent of Message is in the NULL namespace

Will post improved code in a minute
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

Geert BormansInformation ArchitectCommented:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    version="1.0">
    
    <xsl:template match="node()">
        <xsl:copy>
            <xsl:copy-of select="@*"/>
            <xsl:apply-templates select="node()"/>
        </xsl:copy>
    </xsl:template>
    
    <xsl:template match="*[local-name() = 'Message']">
        <Message>
            <xsl:copy-of select="@*"/>
            <xsl:apply-templates select="node()" mode="null-ns"/>
        </Message>
    </xsl:template>

    <xsl:template match="*" mode="null-ns">
        <xsl:element name="{local-name()}">
            <xsl:copy-of select="@*"/>
            <xsl:apply-templates select="node()" mode="null-ns"/>
        </xsl:element>
    </xsl:template>
    
    <xsl:template match="node()[not(self::*)]" mode="null-ns">
        <xsl:copy>
            <xsl:copy-of select="@*"/>
            <xsl:apply-templates select="node()"/>
        </xsl:copy>
    </xsl:template>
    
</xsl:stylesheet>

Open in new window

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Pradeep0308Author Commented:
Geert,

Many thanks. Could you explain me the last two template match what they are doing?

Regards
Pradeep
0
Geert BormansInformation ArchitectCommented:
The first one gets triggered on the Message element and creates a new one but only using the local name (essentialy removing the namespace) and continues processing in a mode. The second one picks up all elements in that mode and removes the namespace for all of them
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
XML

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.