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: XSL logic issue for simple input xml. Please help. This is reply to the solution suggested.
Author: amith swamy
Date: 16 Nov 2007 04:13 AM
Hi,

We have the below issue in XSL logic. We didnt get the reply for our previous issue and hence we are uploading this as a seperate new 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>

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>


The XSL used is as shown below which was suggested in the XSLT forum

<?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>


The above issue worked, but new 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>

Postnext
James DurningSubject: XSL logic issue for simple input xml. Please help. This is reply to the solution suggested.
Author: James Durning
Date: 16 Nov 2007 12:00 PM
Originally Posted: 16 Nov 2007 11:58 AM
To be honest, your source xml should be refactored so that there are none of these problems. A nicer layout would use the xml properly, eg
<root>
<ReservationControlInformationSegment>
<Reservation>
<CompanyId>AAH</CompanyId>
<ReservationControlNumber>ABC456789</ReservationControlNumber>
</Reservation>
<Reservation>
<CompanyId>AAH</CompanyId>
<ReservationControlNumber>ABC456739</ReservationControlNumber>
<ReservationControlType>B</ReservationControlType>
</Reservation>
<Reservation>
<ReservationControlNumber>ABC456740</ReservationControlNumber>
<ReservationControlType>D</ReservationControlType>
</Reservation>
</ReservationControlInformationSegment>
</root>

---
If that's not possible, then can you answer the following?
Which of the elements are required and which are optional for each seperate reservation element? (I would think ReservationControlNumber would be required, but that may not be the case)
Are there any other elements that may appear?
Are they always in the same order?

-------
Assuming they are always in the same order,
Go through each of the tags. You create a new reservation if
Logic:
1. You are a CompanyId
2. You are a ReservationControlNumber without a CompanyId immediately preceding it.
3. You are a ReservationControlType with a ReservationControlType immediately preceding it.

The for-each statement would look something like:
<xsl:for-each select="ReservationControlInformationSegment/*[(name() = 'CompanyID') or (name() = 'ReservationControlNumber' and preceding-sibling::*[1]/name() != 'CompanyID') or (name() = 'ReservationControlType' and preceding-sibling::*[1]/name() = 'ReservationControlType')">
--create new element here

Note, that putting the conditions in the for-each loop is the best way, since you will have the accurate position count afterwards for the reservation.

Postnext
amith swamySubject: XSL logic issue for simple input xml. Please help. This is reply to the solution suggested.
Author: amith swamy
Date: 19 Nov 2007 01:40 AM
Hi,

Thank for your updates.

Source XML cannot be refactored.
We need to change the XSL logic only.

Inside ReservationControlInformationSegment , Elements are CompanyId, ReservationControlNumber, ReservationControlType, FirstDate and Time.

None of the above fields are mandatory.

But the order will be same.

<CompanyId>AAH</CompanyId>
<ReservationControlNumber>ABC456739</ReservationControlNumber>
<ReservationControlType>B</ReservationControlType>
< FirstDate>11OCT2007< /FirstDate>
<Time>1130</Time>

Postnext
amith swamySubject: XSL logic issue for simple input xml. Please help. This is reply to the solution suggested.
Author: amith swamy
Date: 20 Nov 2007 11:10 AM
Hi,

Can anyone please reply to this issue

Postnext
James DurningSubject: XSL logic issue for simple input xml. Please help. This is reply to the solution suggested.
Author: James Durning
Date: 20 Nov 2007 01:09 PM
One more question, if you had:
<CompanyId>AAH</CompanyId>
<ReservationControlNumber>ABC456739</ReservationControlNumber>
<ReservationControlType>B</ReservationControlType>
<FirstDate>11OCT2007< /FirstDate>
<Time>1130</Time>
<ReservationControlNumber>ABC456739</ReservationControlNumber>
<ReservationControlType>B</ReservationControlType>
<FirstDate>11OCT2007< /FirstDate>
<Time>1130</Time>

Would this be:
<RCI01>
<RCI0101>AAH</RCI0101>
<RCI0102>ABC456739</RCI0102>
<RCI0103>B</RCI0103>
<RCI0104>11OCT2007</RCI0104>
<RCI0105>1130</RCI0105>
</RCI01>
<RCI02>
<RCI0202>ABC456739</RCI0102>
<RCI0203>B</RCI0103>
<RCI0204>11OCT2007</RCI0104>
<RCI0205>1130</RCI0105>
</RCI02>

OR would it be:
<RCI01>
<RCI0101>AAH</RCI0101>
<RCI0102>ABC456739</RCI0102>
<RCI0103>B</RCI0103>
<RCI0104>11OCT2007</RCI0104>
<RCI0105>1130</RCI0105>
</RCI01>
<RCI02>
<RCI0201>ABC456739</RCI0102>
<RCI0202>B</RCI0103>
<RCI0203>11OCT2007</RCI0104>
<RCI0204>1130</RCI0105>
</RCI02>
??

Posttop
Minollo I.Subject: XSL logic issue for simple input xml. Please help. This is reply to the solution suggested.
Author: Minollo I.
Date: 20 Nov 2007 03:15 PM
Please do not duplicate posts; your duplicate post has been deleted.

As your question is a generic XSLT question, the Stylus Studio team will most likely not answer it.

General XSLT questions are better asked on the xsl-list email list run by Mulberry Technologies.

 
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-2016 All Rights Reserved.