Hi Charles, thanks for having a look at this for me.
Each optionList/option should be in a unique row.
That row should match the occurrence of the option element under
optionList*/
So if there is a value in the first occurrence of optionList*/ then it
should be displayed in row 1
If you look at the XML under /free-xml you see that optionList1 has 7
array values starting from the first occurrence of optionList1/option.
optionList2 has 10 with a Null value in occurrence 9.
When I apply the stylesheet the display shows the first occurrence of
optionList1 starting from row 3, whereas optionList2 starts from row one
(i.e. matching the occurrence in the XML).
Each unique optionList is the source of a new column (7 in total), and
each occurrence of option within each optionList is the source of a new
row.
The first occurrence of all optionList/options should be on row one.
Do this possibly make more sense?
-----Original Message-----
From: cknell(_at_)onebox(_dot_)com [mailto:cknell(_at_)onebox(_dot_)com]
Sent: 09 March 2006 04:47 PM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: RE: RE: [xsl] FW: XSL processes XML incorrectly when uneven
number of values returned in array elements
Now, I've looked over the relevant part of the stylesheet and I'm still
confused as to what element in the data file should be the source of a
new row and what element should be the source of a new table division.
Can you shed some light on this?
--
Charles Knell
cknell(_at_)onebox(_dot_)com - email
-----Original Message-----
From: Cave, Neil <Neil(_dot_)Cave(_at_)softwareag(_dot_)com>
Sent: Thu, 9 Mar 2006 15:28:06 +0100
To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Subject: RE: RE: [xsl] FW: XSL processes XML incorrectly when uneven
number of values returned in array elements
That is correct...
My apologies for flooding the list with eXcessML
-----Original Message-----
From: cknell(_at_)onebox(_dot_)com [mailto:cknell(_at_)onebox(_dot_)com]
Sent: 09 March 2006 04:26 PM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: RE: [xsl] FW: XSL processes XML incorrectly when uneven
number of values returned in array elements
Actually, Neil, I only really wanted the part of the document that's
causing the problem. After looking over the input, I have made the
hypothesis that the part of the transformation that's troubling you is
the <free-xml> element and its children, is that correct?
--
Charles Knell
cknell(_at_)onebox(_dot_)com - email
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--