[
https://issues.apache.org/jira/browse/CXF-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984803#action_12984803
]
Daniel Kulp commented on CXF-3263:
----------------------------------
I think the current behavior is correct. According to the XMLSchema spec for
double:
http://www.w3.org/TR/xmlschema-2/#double
{code}
double values have a lexical representation consisting of a mantissa followed,
optionally, by the character "E" or "e", followed by an exponent. The exponent
- must- be an integer. The mantissa must be a decimal number. The
representations for exponent and mantissa must follow the lexical rules for
integer and decimal. If the "E" or "e" and the following exponent are omitted,
an exponent value of 0 is assumed.
The special values positive and negative infinity and not-a-number have lexical
representations INF, -INF and NaN, respectively. Lexical representations for
zero may take a positive or negative sign.
For example, -1E4, 1267.43233E12, 12.78e-2, 12 , -0, 0 and INF are all legal
literals for double.
{code}
> DoubleType incorrectly prints scientific notation
> -------------------------------------------------
>
> Key: CXF-3263
> URL: https://issues.apache.org/jira/browse/CXF-3263
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
> Affects Versions: 2.3.1
> Environment: all
> Reporter: Jon Osborn
>
> This issue is directly related to BigDecimalType issue:
> https://issues.apache.org/jira/browse/CXF-2847
> The DoubleType calls Double.toString() which uses scientific notation if the
> value is outside a particular range:
> http://download.oracle.com/javase/6/docs/api/java/lang/Double.html#toString(double)
> This is incorrect. The double type should only include negative sign, period,
> and numbers per the specification.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
