You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Paudi Moriarty (JIRA)" <ji...@apache.org> on 2009/02/27 13:37:12 UTC
[jira] Created: (TAP5-540) Allow exact parsing of numeric client
input by creating a BigDecimal Translator and enabling parseBigDecimal in
DecimalFormat
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
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.
[jira] Closed: (TAP5-540) Allow exact parsing of numeric client
input by creating a BigDecimal Translator and enabling parseBigDecimal in
DecimalFormat
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (TAP5-540) Allow exact parsing of numeric client
input by creating a BigDecimal Translator and enabling parseBigDecimal in
DecimalFormat
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-540:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> 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
>
> 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.
[jira] Closed: (TAP5-540) Allow exact parsing of numeric client
input by creating a BigDecimal Translator and enabling parseBigDecimal in
DecimalFormat
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (TAP5-540) Allow exact parsing of numeric client
input by creating a BigDecimal Translator and enabling parseBigDecimal in
DecimalFormat
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-540:
-----------------------------------------
Assignee: Howard M. Lewis Ship
> 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
>
> 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.
[jira] Commented: (TAP5-540) Allow exact parsing of numeric client
input by creating a BigDecimal Translator and enabling parseBigDecimal in
DecimalFormat
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678974#action_12678974 ]
Howard M. Lewis Ship commented on TAP5-540:
-------------------------------------------
I'm struggling with generating a proper number of right-of-the-decimal digits. It looks like Java's default numberformatter uses three digits of precision. For BigDecimal, we should have infinite digits ... but then we're back to use toString() to parse.
> 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
>
> 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.
[jira] Commented: (TAP5-540) Allow exact parsing of numeric client
input by creating a BigDecimal Translator and enabling parseBigDecimal in
DecimalFormat
Posted by "Paudi Moriarty (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677348#action_12677348 ]
Paudi Moriarty commented on TAP5-540:
-------------------------------------
Currently, I'm using a custom BigDecimal Translator which lacks the localisation features recently introduced. I would prefer not to have to use internal classes to add those features.
> 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
>
> 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.
[jira] Commented: (TAP5-540) Allow exact parsing of numeric client
input by creating a BigDecimal Translator and enabling parseBigDecimal in
DecimalFormat
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678974#action_12678974 ]
Howard M. Lewis Ship commented on TAP5-540:
-------------------------------------------
I'm struggling with generating a proper number of right-of-the-decimal digits. It looks like Java's default numberformatter uses three digits of precision. For BigDecimal, we should have infinite digits ... but then we're back to use toString() to parse.
> 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
>
> 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.
[jira] Commented: (TAP5-540) Allow exact parsing of numeric client
input by creating a BigDecimal Translator and enabling parseBigDecimal in
DecimalFormat
Posted by "Paudi Moriarty (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677348#action_12677348 ]
Paudi Moriarty commented on TAP5-540:
-------------------------------------
Currently, I'm using a custom BigDecimal Translator which lacks the localisation features recently introduced. I would prefer not to have to use internal classes to add those features.
> 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
>
> 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.
[jira] Commented: (TAP5-540) Allow exact parsing of numeric client
input by creating a BigDecimal Translator and enabling parseBigDecimal in
DecimalFormat
Posted by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678982#action_12678982 ]
Thiago H. de Paula Figueiredo commented on TAP5-540:
----------------------------------------------------
Tip: BigDecimal.scale() retuns the number of digits to the right of the decimal point. Then use DecimalFormat.setMinimumFractionDigits() to define the number of digits to the right of the decimal point when formatting.
> 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
>
> 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.
[jira] Commented: (TAP5-540) Allow exact parsing of numeric client
input by creating a BigDecimal Translator and enabling parseBigDecimal in
DecimalFormat
Posted by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678982#action_12678982 ]
Thiago H. de Paula Figueiredo commented on TAP5-540:
----------------------------------------------------
Tip: BigDecimal.scale() retuns the number of digits to the right of the decimal point. Then use DecimalFormat.setMinimumFractionDigits() to define the number of digits to the right of the decimal point when formatting.
> 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
>
> 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.