Return-Path: Delivered-To: apmail-myfaces-dev-archive@www.apache.org Received: (qmail 15834 invoked from network); 23 Feb 2010 18:56:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Feb 2010 18:56:49 -0000 Received: (qmail 1879 invoked by uid 500); 23 Feb 2010 18:56:49 -0000 Delivered-To: apmail-myfaces-dev-archive@myfaces.apache.org Received: (qmail 1804 invoked by uid 500); 23 Feb 2010 18:56:48 -0000 Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Development" Delivered-To: mailing list dev@myfaces.apache.org Received: (qmail 1795 invoked by uid 99); 23 Feb 2010 18:56:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Feb 2010 18:56:48 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Feb 2010 18:56:48 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4D95A29A002B for ; Tue, 23 Feb 2010 10:56:28 -0800 (PST) Message-ID: <1577744356.468161266951388316.JavaMail.jira@brutus.apache.org> Date: Tue, 23 Feb 2010 18:56:28 +0000 (UTC) From: "Gabrielle Crawford (JIRA)" To: dev@myfaces.apache.org Subject: [jira] Updated: (TRINIDAD-1683) client-side convertNumber causes loss of precision In-Reply-To: <1346425903.132961262995014983.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/TRINIDAD-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabrielle Crawford updated TRINIDAD-1683: ----------------------------------------- Resolution: Fixed Fix Version/s: 1.2.14-core Status: Resolved (was: Patch Available) > client-side convertNumber causes loss of precision > -------------------------------------------------- > > Key: TRINIDAD-1683 > URL: https://issues.apache.org/jira/browse/TRINIDAD-1683 > Project: MyFaces Trinidad > Issue Type: Bug > Components: Components > Affects Versions: 1.2.12-core > Reporter: Cale Scholl > Assignee: Gabrielle Crawford > Priority: Minor > Fix For: 1.2.14-core > > Attachments: maxPrecision_1.2.12.2.patch, maxPrecision_trunk.patch > > > ISSUE: > ---------- > JS numbers are 64-bit values and thus only have 16 digits of precision; this isn't enough to represent the max value of a Long, BigInteger, or BigDecimal. This means that when we convert a number string to object then back to string on the client, we can lose precision, even though we wouldn't lose any precision on the server. > FIX: > ----- > Only render a client converter if the input value is bound to a supported type (Float, Double, Integer, Short, Byte). The JavaScript number is a 64-bit floating type and has enough precision to represent any of these supported types. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.