Hi Brian,
the difference in behaviour is caused by an error in the schema that
was previously not detected; 2.7 now finds the schema not valid and,
missing a valid schema, the whitespace cannot be detected as ignorable.
The error is in the declaration
<xsd:element name="root" type="root"/>
that should be written as
<xsd:element name="root" type="root:root"/>
This because every global definition is placed in the target
namespace even if you added elementFormDefault="unqualified" (that is
used only for local element definitions)
Alberto
At 09.45 24/10/2005 -0400, Brian Hassink wrote:
Hi Alberto,
Here are the (subset of) schema and instance documents which create the
whitespace discrepancy between 2.5.0 and 2.7.0...
data/xml/root/root.xml is my instance document and references...
data/xsd/common.xsd
data/xsd/base.xsd
data/xsd/root.xsd
Let me know if I can provide further information.
-Brian
-----Original Message-----
From: Alberto Massari [mailto:[EMAIL PROTECTED]
Sent: Monday, October 24, 2005 4:07 AM
To: [email protected]
Subject: Re: setIncludeIgnorableWhitespace() broken?
Hi Brian,
could you send us the schema and the XML you are using?
Thanks,
Alberto
At 22.42 23/10/2005 -0400, Brian Hassink wrote:
>While working through my recent schema caching issues, I upgraded
>xerces-c from v2.5.0-1 to v2.7.0-0 in my Cygwin environment.
>
>Upon doing this, I noticed that whitespace nodes are inserted in the
>document despite setting
>XercesDOMParser::setIncludeIgnorableWhitespace(false). Has this
>feature been deprecated in the newer release?
>
>-Brian
