-
Bug
-
Resolution: Fixed
-
P4
-
1.2.0
-
1.2.2
-
generic
-
generic
Name: erR10175 Date: 05/01/2002
New JAXP TCK 1.2 test
api/xml_schema/structures/ElemDecl/typeDef/typeDef014/typeDef01401m/typeDef01401m1.html#Negative
fails because the JAXP 1.2 RI allows integer values to be represented in
exponentiation form. In particular the value "1e2" is not valid
representation of the integer value "100", but the parser does not
complain.
The specification (XML Schema Part 2: Datatypes,
3.3.13.1 Lexical representation) reads:
"integer has a lexical representation consisting of a finite-length
sequence of decimal digits (#x30-#x39) with an optional leading sign.
If the sign is omitted, "+" is assumed. For example: -1, 0,
12678967543233, +100000."
The TCK build b06 can be found in the
/java/re/jaxp_tck/1.2/promoted/ea/b06/binaries
location
======================================================================
New JAXP TCK 1.2 test
api/xml_schema/structures/ElemDecl/typeDef/typeDef014/typeDef01401m/typeDef01401m1.html#Negative
fails because the JAXP 1.2 RI allows integer values to be represented in
exponentiation form. In particular the value "1e2" is not valid
representation of the integer value "100", but the parser does not
complain.
The specification (XML Schema Part 2: Datatypes,
3.3.13.1 Lexical representation) reads:
"integer has a lexical representation consisting of a finite-length
sequence of decimal digits (#x30-#x39) with an optional leading sign.
If the sign is omitted, "+" is assumed. For example: -1, 0,
12678967543233, +100000."
The TCK build b06 can be found in the
/java/re/jaxp_tck/1.2/promoted/ea/b06/binaries
location
======================================================================