You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2001/02/28 15:37:04 UTC
[Bug 740] Changed - An error is not raised by the parser for a violation of the constraint minExclusive <= maxExclusive
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=740
*** shadow/740 Tue Feb 27 13:36:37 2001
--- shadow/740.tmp.6978 Wed Feb 28 06:37:04 2001
***************
*** 1,11 ****
+============================================================================+
! | An error is not raised by the parser for the constraint violation minExclu |
+----------------------------------------------------------------------------+
| Bug #: 740 Product: Xerces-J |
| Status: NEW Version: 1.3.0 |
| Resolution: Platform: PC |
| Severity: Normal OS/Version: All |
! | Priority: High Component: Schema-Datatypes |
+----------------------------------------------------------------------------+
| Assigned To: xerces-j-dev@xml.apache.org |
| Reported By: nddelima@ca.ibm.com |
--- 1,11 ----
+============================================================================+
! | An error is not raised by the parser for a violation of the constraint min |
+----------------------------------------------------------------------------+
| Bug #: 740 Product: Xerces-J |
| Status: NEW Version: 1.3.0 |
| Resolution: Platform: PC |
| Severity: Normal OS/Version: All |
! | Priority: Medium Component: Schema-Datatypes |
+----------------------------------------------------------------------------+
| Assigned To: xerces-j-dev@xml.apache.org |
| Reported By: nddelima@ca.ibm.com |
***************
*** 45,47 ****
--- 45,76 ----
Section 4.2.8 of
XML Schema Part 2: Datatypes
W3C Candidate Recommendation 24 October 2000
+
+
+ ------- Additional Comments From nddelima@ca.ibm.com 2001-02-28 06:37 -------
+ Sorry for the inaccuracy while reporting this defect before. Please ignore the
+ information above and see below
+
+ Description: The parser does not raise an error for a simpleType derived by
+ restriction from the Primitive datatype float, with facets minExclusive and
+ maxExclusive where minExclusive>= maxExclusive.
+
+
+ Reference:
+ Constraint on Schemas: minExclusive <= maxExclusive
+ "It is an error for the value specified for minExclusive to be greater than the
+ value specified for maxExclusive for the same datatype"
+
+ Section 4.2.8 of
+ XML Schema Part 2: Datatypes
+ W3C Candidate Recommendation 24 October 2000
+
+
+ Example: The section of code that should have raised an error but did not is as
+ below.
+ <simpleType name="myFloat">
+ <restriction base="float">
+ <minExclusive value="99.99"/>
+ <maxExclusive value="9.99"/>
+ </restriction>
+ </simpleType>