XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
amith swamySubject: Regarding XSLT logic for a simple input XML message
Author: amith swamy
Date: 14 Nov 2007 07:33 AM
Hi,

We are facing below issue in XSL logic. Please help


If input XML has same elements that is repeating twice and should be mapped to the same element in the output XML..
For Ex:

If input XML is,
<?xml version="1.0"?>
<root>
<ReservationControlInformationSegment>
<CompanyId>AAH</CompanyId>
<ReservationControlNumber>ABC456789</ReservationControlNumber>
<CompanyId>AAH</CompanyId>
<ReservationControlNumber>ABC456789</ReservationControlNumber>
<ReservationControlType>B</ReservationControlType>
</ReservationControlInformationSegment>
</root>

In ReservationControlInformationSegment, three elements are there that can repeat any number of times(Consider 2 times). But in the above example for the first time, third element(ReservationControlType) is not present. Second time its present.

The expected output XML is
<root>
<RCI>
<RCI01>
<RCI0101>AAH</RCI0101>
<RCI0102>ABC456789</RCI0102>
</RCI01>
<RCI02>
<RCI0201>AAH</RCI0201>
<RCI0202>ABC456789</RCI0202>
<RCI0203>B</RCI0203>
</RCI02>
</RCI>
</root>

We have used the below XSL to get the output XML

<?xml version='1.0' ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<root>
<RCI>
<xsl:for-each select="root/ReservationControlInformationSegment/CompanyId">
<xsl:variable name="PositionCount" select="position()"/>
<xsl:variable name="this" select="generate-id(.)"/>
<xsl:variable name="next" select="generate-id(following-sibling::ReservationControlNumber[1]/preceding-sibling::CompanyId[1])"/>
<xsl:variable name="reservationcontrolnumber">
<xsl:if test="$this = $next">
<xsl:value-of select="following-sibling::ReservationControlNumber[1]"/>
</xsl:if>
</xsl:variable>
<xsl:variable name="next1" select="generate-id(following-sibling::ReservationControlType[1]/preceding-sibling::CompanyId[1])"/>
<xsl:variable name="reservationcontroltype">
<xsl:if test="$this = $next1">
<xsl:value-of select="following-sibling::ReservationControlType[1]"/>
</xsl:if>
</xsl:variable>
<xsl:variable name="next3" select="generate-id(following-sibling::Time[1]/preceding-sibling::CompanyId[1])"/>
<xsl:variable name="time">
<xsl:if test="$this = $next3">
<xsl:value-of select="following-sibling::Time[1]"/>
</xsl:if>
</xsl:variable>
<xsl:variable name="aReservationControlInformation">RCI<xsl:number value="position()" format="01"/></xsl:variable>
<xsl:element name="{$aReservationControlInformation}">
<xsl:variable name="aCompanyId">RCI<xsl:number value="position()" format="01"/>01</xsl:variable>
<xsl:element name="{$aCompanyId}">
<xsl:value-of select="."/>
</xsl:element>
<xsl:variable name="aReservationControlNumber">RCI<xsl:number value="position()" format="01"/>02</xsl:variable>
<xsl:element name="{$aReservationControlNumber}">
<xsl:value-of select="$reservationcontrolnumber"/>
</xsl:element>
<xsl:variable name="aReservationControlType">RCI<xsl:number value="position()" format="01"/>03</xsl:variable>
<xsl:if test="following-sibling::ReservationControlType[1][normalize-space()]">
<xsl:element name="{$aReservationControlType}">
<xsl:value-of select="$reservationcontroltype"/>
</xsl:element>
</xsl:if>
</xsl:element>
</xsl:for-each>
</RCI></root>
</xsl:template>
</xsl:stylesheet>



But the O/P is in the following format where extra <RCI0103/> is coming
<?xml version="1.0"?>
<root>
<RCI>
<RCI01>
<RCI0101>AAH</RCI0101>
<RCI0102>ABC456789</RCI0102>
<RCI0103/>
</RCI01>
<RCI02>
<RCI0201>AAH</RCI0201>
<RCI0202>ABC456789</RCI0202>
<RCI0203>B</RCI0203>
</RCI02>
</RCI>
</root>


This is because while checking for the if condition we are checking for the following sibling of CompanyId.

Can you please suggest if there is any better approach to solve this problem?

Postnext
James DurningSubject: Regarding XSLT logic for a simple input XML message
Author: James Durning
Date: 14 Nov 2007 10:30 AM
Originally Posted: 14 Nov 2007 10:29 AM
I recommend a modified version of the Muenchian Grouping technique:
Note the key, and the use of it here:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
<xsl:key name="Company" match="*[not(name() = 'CompanyId')]" use="generate-id(preceding-sibling::CompanyId[1])"/>
<xsl:template match="/root">
<root>
<RCI>
<xsl:for-each select="ReservationControlInformationSegment/CompanyId">
<xsl:variable name="PositionCount" select="position()"/>
<xsl:variable name="aReservationControlInformation">RCI<xsl:number value="$PositionCount" format="01"/>
</xsl:variable>
<xsl:variable name="aCompanyId"><xsl:value-of select="$aReservationControlInformation"/>01</xsl:variable>
<xsl:element name="{$aReservationControlInformation}">
<xsl:element name="{$aCompanyId}"><xsl:value-of select="."/></xsl:element>
<xsl:for-each select="key('Company', generate-id(.))">
<xsl:variable name="elementId"><xsl:value-of select="$aReservationControlInformation"/><xsl:number value="1+position()" format="01"/></xsl:variable>
<xsl:element name="{$elementId}">
<xsl:value-of select="."/>
</xsl:element>
</xsl:for-each>
</xsl:element>
</xsl:for-each>
</RCI>
</root>
</xsl:template>
</xsl:stylesheet>

Posttop
amith swamySubject: Regarding XSLT logic for a simple input XML message - updated. please the issue
Author: amith swamy
Date: 15 Nov 2007 06:06 AM
Hi,

Thank you for the udpates.

With the logic mentioned that issue was solved.

But another problem is, if CompanyId tag is only not there, then all the other elements till the next CompanyId will not come in the output.

For ex:

<root>
<ReservationControlInformationSegment>

<ReservationControlNumber>ABC456789</ReservationControlNumber>

<CompanyId>AAA</CompanyId>
<ReservationControlNumber>ABC12345</ReservationControlNumber>
<ReservationControlType>B</ReservationControlType>
</ReservationControlInformationSegment>
</root>

And the o/p will be:

<RCI>
<RCI01>
<RCI0101>AAA</RCI0101>
<RCI0102>ABC12345</RCI0102>
<RCI0103>B</RCI0103>
</RCI01>
</RCI>

And suppose if any of the elements in the middle are missing

For Ex:

<?xml version="1.0"?>
<root>
<ReservationControlInformationSegment>
<CompanyId>AAH</CompanyId>
<ReservationControlNumber>ABC456789</ReservationControlNumber>
<CompanyId>AAA</CompanyId>

<ReservationControlType>B</ReservationControlType>
</ReservationControlInformationSegment>
</root>






In the above example, ReservationControlNumber before ReservationControlType is missing.

Then output will be:

<RCI>
<RCI01>
<RCI0101>AAH</RCI0101>
<RCI0102>ABC456789</RCI0102>
</RCI01>
<RCI02>
<RCI0201>AAA</RCI0201>
<RCI0202>B</RCI0202>
</RCI02>
</RCI>

In the output, in place of ReservationControlNumber, ReservationControlType information will be replaced.
If any information is missing in the middle then empty tag should be there.
But if it is missing at the end, then empty tags need not be there in the output.

For ex:
If four elements should be there in RCI01 and last 2 elements are not present, then empty tags for those 2 elements should not come. But if 2 middle elements are missing then first element should come and middle two elements should come with an empty tag and last element information should be there.

In the above example,

Proper output should be as follows:

<RCI>
<RCI01>
<RCI0101>AAH</RCI0101>
<RCI0102>ABC456789</RCI0102>
</RCI01>
<RCI02>
<RCI0201>AAA</RCI0201>
</RCI0202>
<RCI0203>B </RCI0203>
</RCI02>
</RCI>


 
Topic Page 1 2 3 4 5 6 7 8 9 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2011 All Rights Reserved.