[
https://issues.apache.org/jira/browse/WW-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mitth'raw'nuruodo updated WW-4837:
----------------------------------
Description:
Commit 229afea64e77c2dba9eec62b2c339e9fc92c9ec7 caused all inputs recognisable
as numbers to be formatted with at least one decimal place. This includes all
integers, which is frequently undesirable, particularly if they were meant to
be, eg:
- identifiers, not for arithmetic;
- strictly validated against an XML schema that does not allow for
floating-point numbers;
- subject to length limitations;
- etc
This apparently occurs because all inputs that look like numbers, regardless of
format, are of type {{BigDecimal}} by the time they reach the
{{StringConverter}}.
For our applications, this is a blocker; is it working differently for others?
We don't have any special handling of input types.
was:
Commit 229afea64e77c2dba9eec62b2c339e9fc92c9ec7 caused all inputs recognisable
as numbers to be formatted with at least one decimal place. This includes all
integers, which is frequently undesirable, particularly if they were meant to
be, eg:
- identifiers, not for arithmetic;
- strictly validated against an XML schema that does not allow for
floating-point numbers;
- subject to length limitations;
- etc
This apparently occurs because all inputs that look like numbers, regardless of
format, are of type {{BigDecimal}} by the time they reach the
{{StringConverter}}.
> StringConverter adds a decimal place to integers
> ------------------------------------------------
>
> Key: WW-4837
> URL: https://issues.apache.org/jira/browse/WW-4837
> Project: Struts 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.5.12
> Reporter: Mitth'raw'nuruodo
>
> Commit 229afea64e77c2dba9eec62b2c339e9fc92c9ec7 caused all inputs
> recognisable as numbers to be formatted with at least one decimal place. This
> includes all integers, which is frequently undesirable, particularly if they
> were meant to be, eg:
> - identifiers, not for arithmetic;
> - strictly validated against an XML schema that does not allow for
> floating-point numbers;
> - subject to length limitations;
> - etc
> This apparently occurs because all inputs that look like numbers, regardless
> of format, are of type {{BigDecimal}} by the time they reach the
> {{StringConverter}}.
> For our applications, this is a blocker; is it working differently for
> others? We don't have any special handling of input types.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
