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/14 08:27:44 UTC

[jira] Created: (JCR-1809) Jcr2Spi: Avoid extra round trip to the SPI upon Node.getNode and Session.getItem

Jcr2Spi: Avoid extra round trip to the SPI upon Node.getNode and Session.getItem
--------------------------------------------------------------------------------

                 Key: JCR-1809
                 URL: https://issues.apache.org/jira/browse/JCR-1809
             Project: Jackrabbit
          Issue Type: Improvement
          Components: jackrabbit-jcr2spi
            Reporter: angela
            Assignee: angela


Upon Session.getItem/itemExists and Node.getNode/hasNode JCR2SPI currently tries to load the Node from the persistent layer (SPI) if no corresponding entry exists in the hierarchy.

Since with JCR-1638 a flag has been introduced indicating if the child node entries are complete. In this case, the extra round trip could be omitted.

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

[jira] Resolved: (JCR-1809) Jcr2Spi: Avoid extra round trip to the SPI upon Node.getNode and Session.getItem

Posted by "angela (JIRA)" <ji...@apache.org>.

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

angela resolved JCR-1809.
-------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.0

> Jcr2Spi: Avoid extra round trip to the SPI upon Node.getNode and Session.getItem
> --------------------------------------------------------------------------------
>
>                 Key: JCR-1809
>                 URL: https://issues.apache.org/jira/browse/JCR-1809
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi
>            Reporter: angela
>            Assignee: angela
>             Fix For: 1.5.0
>
>
> Upon Session.getItem/itemExists and Node.getNode/hasNode JCR2SPI currently tries to load the Node from the persistent layer (SPI) if no corresponding entry exists in the hierarchy.
> Since with JCR-1638 a flag has been introduced indicating if the child node entries are complete. In this case, the extra round trip could be omitted.

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