http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2378
*** shadow/2378 Thu Jun 28 07:20:25 2001
--- shadow/2378.tmp.17155 Thu Jun 28 07:27:30 2001
***************
*** 59,62 ****
--- 59,87 ----
Here are the schema and the instance document that cause the errors, as well as
the error I receive from Xerces under JDK 1.3. The instances are a bit long,
and some of the structures might be a little convoluted, so please don't
+ hesitate to write if you're at all confused!
+
+ ------- Additional Comments From [EMAIL PROTECTED] 2001-06-28 07:27 -------
+ In Xerces 1.4.1 attempting to validate an XML document with recursive
+ structures results in the parser, at the first level of recursion (that is to
+ say, <tag><tag>bug is here</tag></tag>), saying that the element is
+ undeclared. What's funny is that, in spite of being "undeclared", the parser
+ also complains that mandatory attributes for the element be present (the
+ attributes DO exist in the instance document) :) What I find strange is that
+ for other simpler documents I have written recursive structures work fine. The
+ choice of parsers has no bearing either: both SAXParser and DOMParser give the
+ same errors. To get the errors, I implemented a very basic error handler that
+ I'm including below in a piece of Java code (actually, this program is the very
+ one that generates the errors).
+
+ Also, there are some datatype validation bugs in Xerces 1.4.1 that are not
+ present in 1.4.0. For example, Xerces treats the same element
+ (<detailedDescription>) as a different datatype in different cases. I have the
+ type declared as xsd:string, but in different positions in the instance
+ document it is treated as a user-defined string type, and even an xsd:float.
+ Again, this problem doesn't exist under Xerces 1.4.0.
+
+ Here are the schema and the instance document that cause the errors, as well as
+ the error I receive from Xerces under JDK 1.3. The instances are a bit long,
+ and some of the structures might be a little convoluted, so please don't
hesitate to write if you're at all confused!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
