[TAP5-540] Allow exact parsing of numeric client input by creating a BigDecimal Translator and enabling parseBigDecimal in DecimalFormat

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.1.0.1
• Fix Version/s: 5.1.0.1
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Paudi Moriarty
• Created: 27/Feb/09 12:35
• Updated: 05/Mar/09 00:08
• Resolved: 05/Mar/09 00:08

Description

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.