XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » XSLT Help and Discussion » Regarding XSLT logic for a simple input XML message
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
+ Stylus Studio Technical Forum (14621)
+ Website Feedback (249)
- XSLT Help and Discussion (7625)
-> + Remove leading Zeros from a st... (4)
-> + how to parse a html element fo... (2)
-> + Add namespaces to target messa... (2)
-> + XSLT Transformation - insertin... (3)
-> + Convert binary xml (9)
-> + XSLT Transformation (4)
-> + Generating hyperlinks (3)
-> + XSLT to PDF problem (with JAVA... (2)
-> + how to add onclick_ with try/c... (2)
-> + Keep table in one page. xsl-fo... (4)
-> + Cannot find a matching 2-argum... (3)
-> + Creating one string from a sub... (2)
-> + XSLT: Traversing XML twice for... (6)
-> + Copy element without namespace... (5)
-> + Create dynamic elemant name (2)
-> + XSLT: Traversing XML twice for... (3)
-> + Problem including Javascript (2)
-> + Looping through attributes (4)
-> + Transform values into elements... (4)
-> + Problem with deep node copy an... (2)
-> + Comparing Dates With ASP.NET 2... (3)
-> + Converting tree structure to h... (4)
-> + Attributes to element transfor... (2)
-> + XSLT transformation (2)
-> + XSLT transformation (5)
-> + xsl:character-map not working (2)
-> + Removing duplicates entries. (2)
-> + Image issues. (2)
-> + xsl transformation (4)
-> + XSL Question (5)
-> + how to insert xml file as an n... (2)
-> + Document Function (2)
-> + convert seconds to hh:mm:ss (5)
-> + how to remove attribute while ... (3)
-> + XSL-FO question (2)
-> + EDI 997 creation. (7)
-> + Line break within a tag in XML... (2)
-> + Contact Help Needed (2)
-> + ACK 997 (2)
-> + XSLT to output XML( which conf... (11)
-> + Retrieving all nodes where a c... (6)
-> + Verifying XML and XSD within X... (4)
-> + How to validate date format in... (3)
-> + XSLT question (2)
-> + Muenchian grouping (2)
-> + How to remove specific text en... (8)
-> + If Else Condition along with L... (2)
-> + SAXON Problem (2)
-> + comapring global variable valu... (2)
-> + copying the value of xsl in va... (2)
-> + Urgent:XSLT element value sel... (2)
-> + Ignoring first element using f... (2)
-> + EDI X12 to XML (4)
-> + XSLT FOR-EACH HELP (2)
-> + Sorting Help Needed (3)
-> + XSLT help with linking (2)
-> + selecting data into node set b... (2)
-> + Watch and Variable in Debug no... (4)
-> + Transforming XML to XML - grou... (2)
-> + Saxon 9.0 B support in debug m... (2)
-> + Repeating element question (2)
-> + Newly Purchased Version Not La... (2)
-> + xsl:include not finding file (5)
-> + JAXP and XSLT 2.0 / XPATH 2.0 (2)
-> + ASP:DropDownList trigger in Xs... (2)
-> + Auto-Skip empty values (2)
-> + retrieving a javascript functi... (2)
-> + need help (2)
-> + html tag ignored (2)
-> + Quick reply needed (8)
-> + xslt to remove namespaces but ... (2)
-> - Using a WSDL definition in an ... (1)
-> + XSL logic issue for simple inp... (6)
-> + Regarding XML namespace prefix... (4)
-> + Mapper reoganizes itself. (8)
-> + XSL Substring Removal (2)
-> - Regarding XSLT logic for a sim... (3)
-> ->Regarding XSLT logic for ...
-> ->Regarding XSLT logic for ...
-> + XSLT Transform documentation (2)
-> + XSLT stack trace in case of er... (3)
-> + No New Line (2)
-> - No New Line (1)
-> + howto loop through a sequence (2)
-> + xml and xsl and whitespace in... (2)
-> + XSL Date formatting (4)
-> + XSL to XSL Mapping using custo... (4)
-> + flat xml to nested xml comvers... (4)
-> + Including schema in scenario (2)
-> + DTDs and traversing (2)
-> + Help with transformation (2)
-> + Problem running XSLT against X... (2)
-> + Carriage return in the output (5)
-> + Generating XSLT to match a sch... (3)
-> + WYSIWYG editor (2)
-> + Grouping without For-Each (3)
-> + output XML using XSLT (8)
-> + Help configuring Xalan-j proce... (8)
-> + Convert Existing HTML pages to... (2)
-> + Generating Transformation - XS... (4)
-> + DOCTYPE public and system info... (2)
-> + Using EXSLT str:tokenize funct... (5)
-- Previous [661-680] [681-700] [701-720] Next
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
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>


   
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.