Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.219.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CF183EC7.13540%anchela@adobe.com>
References: <CF18362D.1350F%anchela@adobe.com>
 <CAOFYJNYi-Bmga5=9U-Syve8caeZ9Vk1XYEvpEO8nxQZOk-D-ow@mail.gmail.com>
 <CF183EC7.13540%anchela@adobe.com>
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Wed, 5 Feb 2014 13:35:15 -0500
Message-ID: 
 <CAOFYJNYv6yKXh-ThuZZOhw3sEx73vxsydE4TQ8hQ2PHu62=yHA@mail.gmail.com>
Subject: Re: Securing Workspace#copy
To: Oak devs <oak-dev@jackrabbit.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

On Wed, Feb 5, 2014 at 1:19 PM, Angela Schreiber <anchela@adobe.com> wrote:
> would we in this case still have the need for Root#copy?
> wouldn't it be better then to just drop that and build
> Workspace#copy in oak-jcr altogether?

That would make sense, yes.

The only case I can see for not doing this would be having an
Oak-based non-JCR repository that doesn't need to worry about things
like access control, versioning or locking. Such a repository could
benefit from a copy-by-reference operation, but for now I'd be happy
to drop the feature at the Oak level and only restore it if/when a new
use case comes along.

BR,

Jukka Zitting