jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edgar Poce <edgarp...@gmail.com>
Subject ItemState existence not cached
Date Wed, 06 Apr 2005 05:11:18 GMT

SharedItemStateManager only caches the existent states and not the 
result of persistMgr.exists(). It causes that when other components in 
jackrabbit asks repeatedly about the existence of an unexistent item 
(calls to ShareditemStateManager.hasNonVirtualItemState) the 
SharedItemStateManager delegates every call to the PM. Is it the 
intended behaviour?


calls to the versioning PM when running core.observation.testAll against 
an empty repository:

nodes destroyed 0
properties destroyed 0
values destroyed 1
node exists: 6576
property exists: 0
node references exists: 0
insert node 1
insert property 1
insert values 1
load node 1
load properties 0
load node references 0
load values 0
store child node entries 1
update node 0
update property 0

View raw message