Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of ianboston@googlemail.com
 designates 209.85.198.231 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=sender:message-id:from:to:content-type:content-transfer-encoding
         :mime-version:subject:date:x-mailer;
        b=SEgJizNMS+bQz4jAWZoD7ZdIzOww2Ic6jiA40YhAFthGxZQ/Om90jH+0yK8MDX88Qi
         /rqylO9x+9QxL6PSjTqRAuvJV7i+MriuhtXwMQIl71r8uCswrhBFkPvCgbM5BHGoTHV8
         b60dTEL0LlC0veuXvVknNOXsToU80anE0rSrk=
Sender: Ian Boston <ianboston@googlemail.com>
Message-Id: <C6EC83E3-5065-4A14-B78E-9208AE76B49A@tfd.co.uk>
From: Ian Boston <ieb@tfd.co.uk>
To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: AccessManager Question.
Date: Thu, 5 Mar 2009 01:26:43 +0000

I have an AccessManager implementation that uses its own session to  
get properties (ACL) on nodes and the parents of nodes that it is  
controlling.

I get lots of
WARN: overwriting cached item b38c5119-2aa2-4e08-b4bf-41dd1720c197  
(2009-03-03 17:10:59,740 TP- 
Processor3_org.apache.jackrabbit.core.ItemManager)

I think this is because the ItemManager is checking with the  
AccessManager, which is adding the item to the cache in ItemManager,  
and when the current thread returns to ItemManager to put the item  
in...... its already been pulled in by AccessManager.. hence the warn.

I am using 1.4.8, I couldn't find anything in jira to help.

So, my questions:

If I want to store ACL's on the nodes, can I use the same session as  
is accessing the node, or do I have to create a second session just  
for accessing the ACL's ?

Will creating a second session per AccessManager have a performance  
impact ?

Ian