Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <10911976.1193421050618.JavaMail.jira@brutus>
Date: Fri, 26 Oct 2007 10:50:50 -0700 (PDT)
From: "Julian Reschke (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Reopened: (JCR-1151) avoid converting property values to
 strings
In-Reply-To: <21569365.1190990930578.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Julian Reschke reopened JCR-1151:
---------------------------------


Change breaks JDK1.4 compliance.


> avoid converting property values to strings
> -------------------------------------------
>
>                 Key: JCR-1151
>                 URL: https://issues.apache.org/jira/browse/JCR-1151
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: SPI
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>
> QValues currently can not expose properties of types LONG and DOUBLE in a parsed format. Thus, setting/retrieving properties of these types requires roundtripping through Strings, which we should avoid.
> Proposal:
> 1) Add "long getLong()" and "double getDouble()" to QValue.
> 2) Add matching create methods to QValueFactory.
> 3) Take advantage of the new methods in JCR2SPI, for instance by allowing it's own Value implementation to internally just hold the QValue.

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