tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Closed: (TAP5-540) Allow exact parsing of numeric client input by creating a BigDecimal Translator and enabling parseBigDecimal in DecimalFormat
Date Thu, 05 Mar 2009 00:09:56 GMT

     [ https://issues.apache.org/jira/browse/TAP5-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-540.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.1.0.1

> Allow exact parsing of numeric client input by creating a BigDecimal Translator and enabling
parseBigDecimal in DecimalFormat
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-540
>                 URL: https://issues.apache.org/jira/browse/TAP5-540
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.1
>            Reporter: Paudi Moriarty
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.1.0.1
>
>
> The current NumericTranslator is great but it is not easy to build on it since the classes
are internal.
> Tapestry should provide a BigDecimal Translator which uses the infrastructure created
for TAP5-211 but parses client input directly to BigDecimal retaining the full precision of
that input.
> For example, I need a client input of 100.00 to be translated to a BigDecimal with value
100.00.  Contributing a NumericTranslator<BigDecimal> results in a BigDecimal with value
100 because the input is parsed to a long by the NumberFormat before being type coerced.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message