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 10 11 12 13 14 15 16 17 18 19 20 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:21 AM
We have a issue in the logic that we have developed for XSL.
Please find the issue below

XSLT issue:

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?


Documentinput(9).xml

Posttop
Tony LavinioSubject: Regarding XSLT logic for a simple input XML message
Author: Tony Lavinio
Date: 14 Nov 2007 10:00 AM
Please do not cross-post.
Followups to: http://www.stylusstudio.com/SSDN/default.asp?action=9&read=7123&fid=48

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 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-2016 All Rights Reserved.