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
Florian SchöllhammerSubject: '=' operator does not work with complex-type with simple-content
Author: Florian Schöllhammer
Date: 18 Aug 2004 01:17 PM
Originally Posted: 18 Aug 2004 10:42 AM
i tried to compare two nodes with the = operator ... it does not work i found out, that the fn:data function does not return anything (the element has a complexType with simpleContent - maybe this is the problem, i do not know!) so i deleted the schema-location in the xml-document and suddenly, the fn:data function return a value! for more detailed information, please view the source code! please help me, why is it like that - did i do something wrong thanks, florian --- EDIT: i could not manage to upload the xquery file ... it seems, as the server is not able to store it! PLEASE DOWNLOAD IT HERE: http://www.schoellhammer.at/complex.xquery


Documentcomplex.xml
Xml Document

Documentcomplex.xsd
Xml Schema

Postnext
Ivan PedruzziSubject: '=' operator does not work with complex-type with simple-content
Author: Ivan Pedruzzi
Date: 18 Aug 2004 11:47 AM
Hi Florian,

The XQuery source didn't make it, try to post it again.

Thank You
Ivan

Postnext
Florian SchöllhammerSubject: '=' operator does not work with complex-type with simple-content
Author: Florian Schöllhammer
Date: 18 Aug 2004 01:18 PM
XQuery File: http://www.schoellhammer.at/complex.xquery

Posttop
Alberto MassariSubject: Re: '=' operator does not work with complex-type with simple-content
Author: Alberto Massari
Date: 19 Aug 2004 03:08 PM
Hi Florian,
there is indeed a problem with fn:data, caused by the fact that the element
has been defined using an anonymous type. A recent change in Xerces has
made so we don't get the type name anymore, and we get confused.
We will need some time to talk with the Xerces team to understand why did
that change, so I cannot forecast when the bug will be fixed; in the
meanwhile you can work around the problem by either extracting the string
value of the element or by changing the schema to use a named global type.

Thanks for reporting this bug,
Alberto


 
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-2016 All Rights Reserved.