jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-1484) Node.getReferences() does not properly reflect saved but not yet committed changes
Date Tue, 18 Mar 2008 13:53:24 GMT

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

Marcel Reutegger resolved JCR-1484.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5

Node.getReferences() now also respects saved but not yet committed references.

Added test cases to XATest.

Fixed in revision: 638363

> Node.getReferences() does not properly reflect saved but not yet committed changes
> ----------------------------------------------------------------------------------
>
>                 Key: JCR-1484
>                 URL: https://issues.apache.org/jira/browse/JCR-1484
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, transactions
>    Affects Versions: 1.4, core 1.4.1, core 1.4.2
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.5
>
>
> Node.getReferences() currently only returns committed references. The specification however
says:
> <quote>
> Some level 2 implementations may only return properties that have been
> saved (in a transactional setting this includes both those properties
> that have been saved but not yet committed, as well as properties that
> have been committed). Other level 2 implementations may additionally
> return properties that have been added within the current Session but are
> not yet saved.
> </quote>
> Jackrabbit does not support the latter, but at least has to support the first.

-- 
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