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 » Stylus Studio Technical Forum » Unexpected for-each behaviour
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + Conerting Excel to XML (5)
-> + count the number of 1 appearin... (10)
-> + Import validation errors (2)
-> + Custom Validation Saxon (4)
-> + How Can i Check if else condit... (2)
-> + Stylus Studio 2009 Ent still b... (2)
-> + cannot download SS2009 (2)
-> + Use of import-schema wants sch... (4)
-> + Replacement Install Media/Bits (3)
-> + XML to Flat File (5)
-> + Select one of multiple attribu... (13)
-> + Web Service - SOAP Error (3)
-> + I find a BUG in stylus studio ... (8)
-> + Text to XML conversion issue (2)
-> + Fixed width flat files (3)
-> + Stylus Studio Crashes when val... (3)
-> + XSL Changes doesn't reflect in... (2)
-> + Custom Conversion Definition T... (6)
-> + Support for UK EDI Tradacoms ... (2)
-> + How to find and remove all ins... (2)
-> + XML to cobol Sequential file (2)
-> + Pipe delimited flat file conve... (2)
-> + Cannot Function Block > DataDi... (3)
-> + License Authentication failed (2)
-> + Flat File Conversion (3)
-> + Struzzo.exe sing 50% of CPU (2)
-> + Saxon9 Transformation error ha... (2)
-> + com.ddtek.xquery3.XQQueryExcep... (10)
-> + XML attribute name (2)
-> + JAVA and XML (2)
-> + DB Connection Error (3)
-> + Dicstionaty Librarys for other... (2)
-> + Passing parameters (3)
-> + Xmlconverter does not work (2)
-> + non-printing characters in Fil... (3)
-> + Including row nos while conve... (5)
-> + Getting Evaluation Copy except... (2)
-> + SS 2008 R2 Bug? (4)
-> + Java Heap Space (2)
-> + generate report from .xsl file... (3)
-> + Can't encode 0x4 in text (3)
-> + Recognize Japanese Characters (2)
-> + converting .xsl to xml using c... (2)
-> - Uninstall doesn't clean up reg... (1)
-> + CDISC (5)
-> - creating database from XML sch... (1)
-> + error: side-by-side configurat... (3)
-> - How to convert pdf into rdf fo... (1)
-> + Apache FOP (5)
-> + XPath Query Editor 'Buggy' (3)
-> - Feature request (1)
-> + XML Convertors (2)
-> + XMLConverters version 3.2.0.0 ... (2)
-> + JVM/stylus studio abort on sav... (3)
-> + using oasis catalog in pipelin... (6)
-> + Another whitespace issue with ... (2)
-> + saxon 9.1.0.2 (2)
-> + xslt change namespace (4)
-> - xslt change namespace (1)
-> + HL7 Conversion (3)
-> + mixed content mapping (2)
-> + HL7 to XML to HL7 (5)
-> + newest version of Saxon SA? (3)
-> + ORM / ORU Seqments (7)
-> + XSLT is causing Java.lang OutO... (3)
-> + Create POJOs from EDI (4)
-> - Embedded message (1)
-> + How to create Documentation fo... (2)
-> + xslt transformation (2)
-> - remove BOM (1)
-> + Changing data as it goes into... (5)
-> + How to (graphically) map one X... (2)
-> + Stylus Studio 2008 Release 2 -... (2)
-> + keyboard shortcuts to switch b... (2)
-> + Help with getting Output XML f... (8)
-> + Document created from schema (2)
-> + XSD Validation error (2)
-> + Set the value of an attribute ... (2)
-> + Saving as XML, Source Data Typ... (2)
-> + Own templates in file/new (4)
-> + Does Stylus Studio support the... (2)
-> - How to transform XML file to T... (1)
-> + Extract XML file from a HTML s... (2)
-> + Crashing, high cpu usage, larg... (6)
-> + Creating an xml document based... (2)
-> + Problem with restriction (2)
-> + EDI Invalid date time error (2)
-> + How to Compose a Web Service C... (5)
-> + Java Complie errors with XML C... (2)
-> + Creating xml file from CSV uss... (4)
-> + XML Converters (6)
-> + schema validation (15)
-> - 9/30 Customer Showcase Webinar... (1)
-> + ETL (2)
-> + xsd:sequence question (3)
-> + contains an invalid path (5)
-> - Custom converter to map flat f... (1)
-> + validating a 4.01 transitional... (2)
-> + Cannot Use Stylus Studio On Mu... (5)
-> + Missing DB to XML option (2)
-- Previous [901-920] [921-940] [941-960] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2017)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Postnext
(Deleted User) Subject: Unexpected for-each behaviour
Author: (Deleted User)
Date: 09 Jun 2003 10:23 AM
I'm mapping an xCBL invoice to a BASDA Invoice.
Obviously the expected output would be:

InvoiceHeader
InvoiceLine
InvoiceLineNumber1
InvoiceLineItem1
InvoiceLine
InvoiceLineNumber2
InvoiceLineItem2
InvoiceLine
InvoiceLineNumber3
InvoiceLineItem3
InvoiceFooter

but instead I am getting

InvoiceHeader
InvoiceLine
InvoiceLineNumber1
InvoiceLineNumber2
InvoiceLineNumber3
InvoiceLineItem1
InvoiceLineItem2
InvoiceLineItem3
InvoiceFooter

Any ideas?
I've mapped the orders for these specifications successfully so why this?
I've attached the docs.

Thx


DocumentxCBL.Invoice.Schema(1).xsd
Source schema (xCBL)

Documentinvoice-v3(1).xsd
Destination schema (BASDA)

DocumentInvoice-xCBL-BASDA1.xsl
Map

Document526e1272-78b0-1000-8e1a-c0a80ad70001(1).xml
Test doc
Postnext
(Deleted User) Subject: RE: Unexpected for-each behaviour
Author: (Deleted User)
Date: 09 Jun 2003 11:10 AM
are you saying the mapper generated wrong xsl or the the xsl looks fine but
the processor produce an unexpected result?

from what you described, I assume that you link all the source element
inclduing InvoiceLineNumber1, InvoiceLineNumber2, InvoiceLineNumber3,
InvoiceLineItem1, InvoiceLineItem2
, InvoiceLineItem3 into the target element InvoiceLine? but if you really
need 3 seperated InvoiceLine, you need to use 'DuplicateNode' feature to
create 3 seperate InvoiceLine and link InvoiceLineNumber1 and
InvoiceLineItem1 into the first, InvoiceLineNumber2 and InvoiceLineItem2
into second InvoiceLine and so on..

please clarify if this is not what you mean?

song


> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager@edn.exln.com]
> Sent: Monday, June 09, 2003 10:45 AM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: Unexpected for-each behaviour
>
>
> From: "Chris Lindley"
>
> I'm mapping an xCBL invoice to a BASDA Invoice.
> Obviously the expected output would be:
>
> InvoiceHeader
> InvoiceLine
> InvoiceLineNumber1
> InvoiceLineItem1
> InvoiceLine
> InvoiceLineNumber2
> InvoiceLineItem2
> InvoiceLine
> InvoiceLineNumber3
> InvoiceLineItem3
> InvoiceFooter
>
> but instead I am getting
>
> InvoiceHeader
> InvoiceLine
> InvoiceLineNumber1
> InvoiceLineNumber2
> InvoiceLineNumber3
> InvoiceLineItem1
> InvoiceLineItem2
> InvoiceLineItem3
> InvoiceFooter
>
> Any ideas?
> I've mapped the orders for these specifications successfully so why this?
> I've attached the docs.
>
> Thx
>
>
>
> To reply: mailto:stylus-studio-tech.6762@edn.exln.com
> To start a new topic: mailto:stylus-studio-tech@edn.exln.com
> To login: http://edn.exln.com/~SSDN
>
Postnext
(Deleted User) Subject: RE: Unexpected for-each behaviour
Author: (Deleted User)
Date: 09 Jun 2003 12:03 PM
Song, you are correct in your assumption of my desired result and yes I do link all the child elements to their corresponding destinations. But this duplicating node feature is of no use as the number of invoice lines is purely random.

I've attached the schemas, map and test doc for the BASDA order to xCBL order which works fine. You'll see no node duplicating in the destination schema yet it still generates two order lines as in the source doc.

Thx.


Documentorder-v3(1).xsd
Source Schema (BASDA)

DocumentxCBL.Order.Schema(1).xsd
Destination schema

DocumentOrder-BASDA-xCBL(1).xsl
Map

Documenttest(3).xml
Test doc
Posttop
(Deleted User) Subject: RE: Unexpected for-each behaviour
Author: (Deleted User)
Date: 09 Jun 2003 12:26 PM
Chris,

as you see, duplicate node is not helpful if the duplication is not fixed.
this is a limitation of mapper. like we discussed before, what you really
need is a conditional mapping which create different output based on
different condition. we don't have this feature yet.

as your test case, I think you are talking about the result xml has multiple
. this is because you have for-each in your stylesheet which
could, obviously, create multiple element depends on your source. in this
case, your mapping didn't involve structure change which means you know your
will repeat based on the same transformation logic.

again, if you want different transformation logic for different
and the number of is fixed, you can use 'duplicate node'.
otherwise, you can't do it in GUI until we have the conditional mapping
functionality.


hope this help.

song.


> -----Original Message-----
> From: stylus-studio-tech Listmanager [mailto:listmanager@edn.exln.com]
> Sent: Monday, June 09, 2003 12:24 PM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: RE: Unexpected for-each behaviour
>
>
> From: "Chris Lindley"
>
> Song, you are correct in your assumption of my desired result and
> yes I do link all the child elements to their corresponding
> destinations. But this duplicating node feature is of no use as
> the number of invoice lines is purely random.
>
> I've attached the schemas, map and test doc for the BASDA order
> to xCBL order which works fine. You'll see no node duplicating in
> the destination schema yet it still generates two order lines as
> in the source doc.
>
> Thx.
>
>
>
> To reply: mailto:stylus-studio-tech.6764@edn.exln.com
> To start a new topic: mailto:stylus-studio-tech@edn.exln.com
> To login: http://edn.exln.com/~SSDN
>
   
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.