jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2234) changed behavior of javax.jcr.Value get* methods
Date Wed, 29 Jul 2009 14:43:15 GMT

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

Stefan Guggisberg updated JCR-2234:
-----------------------------------

      Description: 
stream handling semantics of javax.jcr.Value has been simplified in JCR 2.0:

Section '5.10.5.1 Deprecated Binary Behavior'

[...]
Unlike in JCR 1.0, calling a get method other than getStream before 
calling getStream on the same Value object will never cause an 
IllegalStateException. 


see https://jsr-283.dev.java.net/issues/show_bug.cgi?id=658
    Fix Version/s: 2.0.0

> changed behavior of javax.jcr.Value get* methods
> ------------------------------------------------
>
>                 Key: JCR-2234
>                 URL: https://issues.apache.org/jira/browse/JCR-2234
>             Project: Jackrabbit Content Repository
>          Issue Type: Sub-task
>            Reporter: Stefan Guggisberg
>            Assignee: Stefan Guggisberg
>             Fix For: 2.0.0
>
>
> stream handling semantics of javax.jcr.Value has been simplified in JCR 2.0:
> Section '5.10.5.1 Deprecated Binary Behavior'
> [...]
> Unlike in JCR 1.0, calling a get method other than getStream before 
> calling getStream on the same Value object will never cause an 
> IllegalStateException. 
> see https://jsr-283.dev.java.net/issues/show_bug.cgi?id=658

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


Mime
View raw message