Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <14006443.1166787085933.JavaMail.jira@brutus>
Date: Fri, 22 Dec 2006 03:31:25 -0800 (PST)
From: "Stefan Guggisberg (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-680) Improve the Value implementation
In-Reply-To: <16093243.1166352080958.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/JCR-680?page=comments#action_12460441 ] 
            
Stefan Guggisberg commented on JCR-680:
---------------------------------------

> * Support for namespace remappings in NAME and PATH values 

is this a requirement? IMO the spec doesn't mandate it. 

a first rough run through the (btw huge!) patch revealed 2 issues:

- SerializableInputStream: 
  the stream data is materialized in memory during de-/serialization;
  this renders it imo unusable for large streams. in the entire core
  streams are never unconditionally materialized. 

- ValueParser:
   the getDate() method does not preserve the time zone in the 
   returned Calendar object. the current implementation internally
   uses to ISO8601 utilty class which preserves the time zone  
   information. what was the rationale of not using the ISO8601 class?


> Improve the Value implementation
> --------------------------------
>
>                 Key: JCR-680
>                 URL: http://issues.apache.org/jira/browse/JCR-680
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jukka Zitting
>         Assigned To: Jukka Zitting
>            Priority: Minor
>         Attachments: class.jpg, JCR-680.patch
>
>
> The current Value implementation found in jackrabbit-jcr-commons has some deficiencies like Value.equals() being incorrect in some cases (see for example JCR-320), and Name and Path values not following namespace remappings.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira