You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2010/02/23 01:45:30 UTC
[jira] Created: (JCR-2511) Value#getBinary() and #getStream()
return internal representation for type PATH and NAME
Value#getBinary() and #getStream() return internal representation for type PATH and NAME
----------------------------------------------------------------------------------------
Key: JCR-2511
URL: https://issues.apache.org/jira/browse/JCR-2511
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core
Affects Versions: 2.0.0
Reporter: angela
just found a path-related spi2dav test failing that passed some time before jackrabbit 2.0 (BatchTest#testSetPathValue).
i had a quick look at it and it seems to me that the reasons is the internal (Path, Name) value representation
being exposed when calling Value#getBinary(), Value#getStream() and the corresponding shortcuts on Property.
from my understanding of the specification these methods should always return the standard JCR path (or name) representation as it
is exposed by Value#getString() and Property#getString() as it used to be in previous versions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2511) Value#getBinary() and #getStream()
return internal representation for type PATH and NAME
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg updated JCR-2511:
-----------------------------------
Component/s: (was: jackrabbit-core)
jackrabbit-jcr-commons
Priority: Minor (was: Major)
> Value#getBinary() and #getStream() return internal representation for type PATH and NAME
> ----------------------------------------------------------------------------------------
>
> Key: JCR-2511
> URL: https://issues.apache.org/jira/browse/JCR-2511
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-commons
> Affects Versions: 2.0.0
> Reporter: angela
> Priority: Minor
>
> just found a path-related spi2dav test failing that passed some time before jackrabbit 2.0 (BatchTest#testSetPathValue).
> i had a quick look at it and it seems to me that the reasons is the internal (Path, Name) value representation
> being exposed when calling Value#getBinary(), Value#getStream() and the corresponding shortcuts on Property.
> from my understanding of the specification these methods should always return the standard JCR path (or name) representation as it
> is exposed by Value#getString() and Property#getString() as it used to be in previous versions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2511) Value#getBinary() and #getStream()
return internal representation for type PATH and NAME
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg resolved JCR-2511.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
fixed in svn r 918915
> Value#getBinary() and #getStream() return internal representation for type PATH and NAME
> ----------------------------------------------------------------------------------------
>
> Key: JCR-2511
> URL: https://issues.apache.org/jira/browse/JCR-2511
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-commons
> Affects Versions: 2.0.0
> Reporter: angela
> Priority: Minor
> Fix For: 2.1.0
>
>
> just found a path-related spi2dav test failing that passed some time before jackrabbit 2.0 (BatchTest#testSetPathValue).
> i had a quick look at it and it seems to me that the reasons is the internal (Path, Name) value representation
> being exposed when calling Value#getBinary(), Value#getStream() and the corresponding shortcuts on Property.
> from my understanding of the specification these methods should always return the standard JCR path (or name) representation as it
> is exposed by Value#getString() and Property#getString() as it used to be in previous versions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.