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
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)
-> ->XSL logic issue for simpl...
-> ->XSL logic issue for simpl...
-> ->XSL logic issue for simpl...
-> ->XSL logic issue for simpl...
-> ->XSL logic issue for simpl...
-> + Regarding XML namespace prefix... (4)
-> + Mapper reoganizes itself. (8)
-> + XSL Substring Removal (2)
-> + Regarding XSLT logic for a sim... (3)
-> + 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: 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.

   
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.