Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of
 daniel.mitterdorfer@salzburgresearch.at designates 212.183.10.131 as
 permitted sender)
Message-ID: <474287BF.8000900@salzburgresearch.at>
Date: Tue, 20 Nov 2007 08:07:43 +0100
From: Daniel Mitterdorfer <daniel.mitterdorfer@salzburgresearch.at>
Organization: Salzburg Research Forschungsgesellschaft
User-Agent: Thunderbird 1.5.0.13 (Windows/20070809)
MIME-Version: 1.0
To: users@jackrabbit.apache.org
Subject: Re: XPath query returns no results
References: <47417531.4050002@salzburgresearch.at> <47418DAA.8030403@gmx.net>
 <47419633.6080005@salzburgresearch.at> <47419ECB.5030802@gmx.net>
In-Reply-To: <47419ECB.5030802@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Marcel,

I just verified your assumption: You were absolutely right. I was not 
aware that the XPath queries only run against committed results. Because 
my #dump() returned all expected nodes right before I issued the XPath 
query I thought it would also take these nodes into account. Thanks a 
lot to all for your help, especially to you, Marcel!

Bye,

Daniel

Marcel Reutegger wrote:
> Hi Daniel,
>
> ah, now I'm starting to realize what happens. You are using spring 
> modules, which probably wraps a transaction around your code. because 
> queries are only run against *committed* content it may happen that 
> you won't see results even though you saved (but not yet committed) 
> changes. this is somewhat counter intuitive and has been debated on 
> this list a while ago. JSR 283 will be more flexible in this respect.
>
> can you please make sure you commit the transaction before you execute 
> the query? that will probably solve your issue.
>
> regards
>  marcel
>