[
https://issues.apache.org/jira/browse/WW-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012259#comment-16012259
]
ASF GitHub Bot commented on WW-3171:
------------------------------------
Github user cnenning commented on the issue:
https://github.com/apache/struts/pull/138
In our apps we have often demand for locale aware values. But more often we
need dates, not doubles. Mostly we do this by calling java methods in JSPs. But
having converts which do this out of the box would be great.
> Will this break apps with locales which are using different decimal
separator?
Yes, for some apps that would be a breaking change. But IMHO most apps use
number formats which their users expect (-> locale aware number format). So for
most it would be an improvement and they could remove custom code. But still,
some apps might be broken.
I always find it hard to get java `NumberFormat` and `ParsePositon` right.
Not sure if there are subtle bugs in this PR. But there are lots of tests so
hopefully all corner cases are covered 😉
> "double" and "Double" are not validated with the same decimal séparator
> -----------------------------------------------------------------------
>
> Key: WW-3171
> URL: https://issues.apache.org/jira/browse/WW-3171
> Project: Struts 2
> Issue Type: Bug
> Components: Core Actions
> Affects Versions: 2.0.14
> Environment: Windows or Linux - Running under Tomcat 6.0 - fr_FR
> Reporter: françois-frédéric jean
> Assignee: Lukasz Lenart
> Priority: Critical
> Fix For: 2.5.next
>
>
> I had this strange behaviour.
> I have two double in my Action (extends ActionSupport):
> ---------------------------
> private double dbl1;
> private Double dbl2;
> ---------------------------
> With there respective getters and setters.
> But, when I call the action with these two doubles (from a classical HTML
> form), I must put a "dot" for the double, and a "comma" for the Double as a
> decimal separator,
> I'm surprised by this behaviour .... Nothing particular was done (HTML form
> calling an action). I can't imagine what is the reason of this behaviour, so
> I raise it as a bug.
> Regards
> Francillo
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
