You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2008/03/18 14:19:24 UTC
[jira] Created: (JCR-1484) Node.getReferences() does not properly
reflect saved but not yet committed changes
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: core 1.4.1, 1.4
Reporter: Marcel Reutegger
Priority: Minor
Fix For: core 1.4.2
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.
[jira] Updated: (JCR-1484) Node.getReferences() does not properly
reflect saved but not yet committed changes
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-1484:
----------------------------------
Fix Version/s: (was: core 1.4.2)
Affects Version/s: core 1.4.2
> 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.
[jira] Resolved: (JCR-1484) Node.getReferences() does not properly
reflect saved but not yet committed changes
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (JCR-1484) Node.getReferences() does not properly
reflect saved but not yet committed changes
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-1484:
-------------------------------
Fix Version/s: (was: 1.5)
core 1.4.3
Merged to the 1.4 branch in revision 650336.
> 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: core 1.4.3
>
>
> 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.