Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: domain of stefan.guggisberg@gmail.com
 designates 66.249.92.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=TYEr08n3m0uw2d3b2G/FO0DCZJcC5fVEB0pxuw8rJXZaMKte9tKaqgY5Ov8RgaKK5fgqdBPdAJBsR/nGOPn9GXZFy+2TCSzUrfXf50MYECZ8R7d2ltZm6uxXBc9MWWPlTdPukZvnVVoILFGReaPX/Rft3w8eM0fB+eKDzSSmdGw=
Message-ID: <90a8d1c00705230244r6dccc156j6ff44efb9d8aeae0@mail.gmail.com>
Date: Wed, 23 May 2007 11:44:04 +0200
From: "Stefan Guggisberg" <stefan.guggisberg@gmail.com>
To: dev@jackrabbit.apache.org
Subject: Re: session.move vs. workspace.move
In-Reply-To: <3b728ee90705211216x1583c020o608a1a7dbf7eaf2a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <3b728ee90705211216x1583c020o608a1a7dbf7eaf2a@mail.gmail.com>

hi christophe

On 5/21/07, Christophe Lombart <christophe.lombart@gmail.com> wrote:
> Hi all,
>
> In the ocm framework, we have the feature to move object. When the
> implementation uses the jcr call 'session.move (src, dst)', it works fine.
> the source node is deleted but if the implementation used the jcr call '
> workspace.move(src, dst)', the source node is not deleted.
> I'm wondering why the both methods are not providing the same result. Is it
> not a bug or do I miss something ?

the difference between Session#move and Workspace#move is that the
latter immediately persists the changes while the former causes transient
changes only (which need to be persisted separatly using a save() call).

however, the current session's resulting view should be the same.

personally i doubt that it's a bug in Workspace#move since we should
have noticed it earlier. however, if you have a test case that demonstrates
the issue please create a jira issue.

cheers
stefan
>
> br,
> Christophe
>