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 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Michael HincheySubject: XSLT mapper shows XSD with recursion
Author: Michael Hinchey
Date: 18 Jan 2002 12:48 PM
I defined an XSD with a reuse of element names. The XSD is valid according to Stylus. The XSD tree editor displays it correctly. Stylus reports a valid XML to be valid. However, the XSLT Mapper displays the XSD as a tree with infinite recursion. An XML example of that is (correctly) reported by Stylus to be invalid.

The XSD and example XML files are attached.

Thanks,
Mike


Documentexamples.txt
Example XSD and XML valid and invalid

Posttop
(Deleted User) Subject: XSLT mapper shows XSD with recursion
Author: (Deleted User)
Date: 18 Jan 2002 01:39 PM
This is a multi-part message in MIME format.

------=_NextPart_000_0006_01C1A027.3D957BE0
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi, Michael



Thank you for your test case, we can reproduce the problem. As you
described, allow second 'one' element to recursively open is not right.
This is happening because mapper mistakenly thinks the second 'one' is
of the same type as the first 'one'. We'll file a PCR and work on this
issue.



By the way, would that be a good idea to use different element name in
complex type 'big' rather than use 'one' and 'two' which is already
defined somewhere else...





Song.




------=_NextPart_000_0006_01C1A027.3D957BE0
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

















Hi, style='font-size:10.0pt;font-family:"Courier =New"'>Michael



 



Thank you for your test case, we can =reproduce the
problem. As you described, allow second ‘one’ element to
recursively open is not right. This is happening because mapper =mistakenly
thinks the second ‘one’ is of the same type as the first =‘one’.
We’ll file a PCR and work on this issue.



 



By the way, would that be a good idea to use =different
element name in complex type ‘big’ rather than use =‘one’
and ‘two’ which is already defined somewhere =else...



 



 



Song.



 









------=_NextPart_000_0006_01C1A027.3D957BE0--

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 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-2011 All Rights Reserved.