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/09 17:08:44 UTC

[jira] Created: (JCR-1798) JCR2SPI: Avoid individual Item reloading upon Session/Item.refresh(true)

JCR2SPI: Avoid individual Item reloading upon Session/Item.refresh(true)
------------------------------------------------------------------------

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


with CacheBehaviour.INVALIDATE Item.refresh(true) and Session.refresh(true) results in individual reloading of the existing entries in the hierarchy circumventing all batch read optimization.

Apart from general optimization of the refresh itself, refresh(true) should rather mark existing items and force a reload upon next access (similar to the behaviour implemented with refresh(false)).



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

[jira] Resolved: (JCR-1798) JCR2SPI: Avoid individual Item reloading upon Session/Item.refresh(true)

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

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

angela resolved JCR-1798.
-------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.0
         Assignee: angela

> JCR2SPI: Avoid individual Item reloading upon Session/Item.refresh(true)
> ------------------------------------------------------------------------
>
>                 Key: JCR-1798
>                 URL: https://issues.apache.org/jira/browse/JCR-1798
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-jcr2spi
>            Reporter: angela
>            Assignee: angela
>             Fix For: 1.5.0
>
>
> with CacheBehaviour.INVALIDATE Item.refresh(true) and Session.refresh(true) results in individual reloading of the existing entries in the hierarchy circumventing all batch read optimization.
> Apart from general optimization of the refresh itself, refresh(true) should rather mark existing items and force a reload upon next access (similar to the behaviour implemented with refresh(false)).

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