Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of jreschke@adobe.com designates
 64.18.1.23 as permitted sender)
Message-ID: <4FA7EB8E.4030701@adobe.com>
Date: Mon, 7 May 2012 17:34:38 +0200
From: Julian Reschke <jreschke@adobe.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Subject: session visibility
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

I was looking into

   SessionRemoveItemTest#testRemoveItem3()

where we test that a separate session B can still read a node while the 
other session A has removed but not saved it.

In this case, B is instantiated *before* the test setup actually created 
the test node using session A. So session B doesn't see it not because 
it was removed but because it wasn't there in the first place when the 
session was created.

Sure enough, the test passes if we add a refresh() on B before the check.

I *believe* this is indeed a bug in the test case, but wanted to 
double-check what the current behavior is indeed by design, and that 
we're not planning to change it.

If this is true, we probably should open a JCR JIRA issue for tracking 
these kind of problems in the (former) TCK (that is, jackrabbit-jcr-tests).

Best regards, Julian