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 » DESADV D96A Schema vs XML inconsistency
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> + Call Web Service, Nothing retu... (12)
-> + Error while debugging xslt wit... (2)
-> - DESADV D96A Schema vs XML inco... (4)
-> ->DESADV D96A Schema vs XML...
-> ->DESADV D96A Schema vs XML...
-> ->DESADV D96A Schema vs XML...
-> + Das Programm mit mysql ? (4)
-> + RegEx Search and Replace (6)
-> + SequeLink Server - Do I need a... (6)
-> + faultString: (401)Unauthorized... (7)
-> + Previewing XSL with javascript... (2)
-> + removing formating from XML (6)
-> + removing formating from XML (2)
-> + Custom EDI to XML conversion (2)
-> + Getting "Type not found" error... (4)
-> - Converting file and customize ... (1)
-> + formatting problem with xml ex... (2)
-> + Using DTD Entities and XSD (7)
-> + XML Schema (XSD), Adding comme... (2)
-> + DTD schema generation problem (2)
-> + How do i generate a schema fro... (4)
-> + Incomplete request message gen... (2)
-> + Installation issue for Stylus ... (2)
-- Previous [1741-1760] [1761-1780] [1781-1800] 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
Oddbjørn OverskottSubject: DESADV D96A Schema vs XML inconsistency
Author: Oddbjørn Overskott
Date: 05 Feb 2007 08:37 AM
There is an inconsistency between the XSD schema and the generated XML for a DESADV D96A message. This problem can be demonstrated by converting the enclosed desadv-message to XML using the EDI adapter. You have to disable the "Force error if value not in codelist" option, and set the "Use long element names" option. The generated XML contains a PAC subsegment named PAC03-PackagingDetails, while the XSD specifies PAC02-PackagingDetails and PAC03-PackageType. This applies to StylusStudio 2007 version 735f.


DocumentTamroDesAdv.EDI
Sample DESADV D96A file
Postnext
Tony LavinioSubject: DESADV D96A Schema vs XML inconsistency
Author: Tony Lavinio
Date: 06 Feb 2007 01:49 AM
Thanks. We'll take a look and see what needs to be done.
Postnext
Oddbjørn OverskottSubject: DESADV D96A Schema vs XML inconsistency
Author: Oddbjørn Overskott
Date: 06 Feb 2007 05:32 AM
Another one in DESADV D96A: For the FTX segment in GROUP_15, the XSD says FTX03-TextReference and FTX04-TextLiteral, while the generated XML contains FTX04-TextReference.
Posttop
Tony LavinioSubject: DESADV D96A Schema vs XML inconsistency
Author: Tony Lavinio
Date: 08 Feb 2007 11:55 AM
The schema is correct; the adapter is pulling the long name
from the neighboring component element. This will be fixed
for the next release.
   
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.