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 2008/10/30 18:10:44 UTC

[jira] Resolved: (JCR-1819) JCR2SPI: Add specific deep loading of Nodes and Properties

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

angela resolved JCR-1819.
-------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.0

> JCR2SPI: Add specific deep loading of Nodes and Properties
> ----------------------------------------------------------
>
>                 Key: JCR-1819
>                 URL: https://issues.apache.org/jira/browse/JCR-1819
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi
>            Reporter: angela
>            Assignee: angela
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> with jcr2spi an item is 'deep' loaded whenever the hierarchy is not complete. while for Session#itemExists or Session#getItem it is ok to try loading a Node first and if not found a Property, this is inconvenient (and generates unnecessary round trips to the SPI) for those cases, where the original JCR call indicates whether a Node or Property is expected.
> This is the case for Node.getNode(String relPath) and Node.getProperty(String relPath) ((and maybe others))
> Therefore i suggest to add specific methods
> HierarchyManager#getNodeEntry
> HierarchyManager#getPropertyEntry
> NodeEntry#getDeepNodeEntry
> NodeEntry#getDeepPropertyEntry
> (or something similar)

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