From oak-dev-return-533-apmail-jackrabbit-oak-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Tue Apr 3 10:19:02 2012 Return-Path: X-Original-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Delivered-To: apmail-jackrabbit-oak-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 37319920F for ; Tue, 3 Apr 2012 10:19:02 +0000 (UTC) Received: (qmail 65230 invoked by uid 500); 3 Apr 2012 10:19:02 -0000 Delivered-To: apmail-jackrabbit-oak-dev-archive@jackrabbit.apache.org Received: (qmail 65193 invoked by uid 500); 3 Apr 2012 10:19:02 -0000 Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oak-dev@jackrabbit.apache.org Delivered-To: mailing list oak-dev@jackrabbit.apache.org Received: (qmail 65185 invoked by uid 99); 3 Apr 2012 10:19:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Apr 2012 10:19:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jukka.zitting@gmail.com designates 74.125.82.170 as permitted sender) Received: from [74.125.82.170] (HELO mail-we0-f170.google.com) (74.125.82.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Apr 2012 10:18:55 +0000 Received: by werh12 with SMTP id h12so4777286wer.1 for ; Tue, 03 Apr 2012 03:18:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=k8LOu8J5KtJ971iJuPJw2yln/kTS8tZZ7IIc5tmXNGI=; b=e321JS2cwJ0QpP5eFEjwdV8bJoVU8JtzjMil1knhTerocIli66vuND+O+j06QtplmZ WXG9QXrMkPz38dFjEv5zB0eFImcCfPrPEzweSo22axWzxffSoB707xWxF20EhbtgQaZ/ d/3HQ207oltfOrRJ7kMsl6ZLdyea1Y0SlNGlCMuqPV76Kg07mok8tLi7iu8C1Qw/9A5J rX8/SKLhc8bwJ7tZpzTGZ6K6VxMf8Oa4DgxEomnjvmgB3Zdi8bVKaKtabIwLEgPFsy7G NT+kE3RRCyWbYR7j/jBT7xt+CsOUBWLV8y0bEgem97xYwDisJUJJPOS/La6NESS2N9fK /PHg== Received: by 10.180.95.34 with SMTP id dh2mr35021200wib.15.1333448314544; Tue, 03 Apr 2012 03:18:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.84.199 with HTTP; Tue, 3 Apr 2012 03:18:14 -0700 (PDT) In-Reply-To: <4F7ACC0D.2020702@adobe.com> References: <4F74D366.2050503@gmail.com> <4F75A19C.4020109@apache.org> <4F787046.3090403@apache.org> <4F7AC198.1000403@adobe.com> <4F7ACC0D.2020702@adobe.com> From: Jukka Zitting Date: Tue, 3 Apr 2012 12:18:14 +0200 Message-ID: Subject: Re: oak-api and move operations To: oak-dev@jackrabbit.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi, On Tue, Apr 3, 2012 at 12:08 PM, Angela Schreiber wrote: > well... looking at the current oak-jcr i still see > revision = microkernel.commit("", changeLog.toJsop(), revision, ""); > > this means to me that we still don't have a clear separation > of the different layer as we discussed it multiple times in the > past. Ah, I see your point and totally agree. My intention is not to expose this directly to the oak-jcr level. It needs to work through the Oak API as exposed by oak-core. BR, Jukka Zitting > if anyone else that the SPI layer has access to the MK this is just > a completely different setup that requires fundamental changes in > the way we envision the jr3 security concept. > > but maybe i just got sidetracked by the current code in relation > to that discussion ... i don't mind having extra stuff on the mk-api > if it fits our needs > > kind regards > angela