Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of mrduguo@gmail.com designates
 209.85.218.220 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=H7OomctvXnR7xB+Cade5vLFT/3duEDvA1Yi26o4fMHvx7Ov94tZ79l4z9mZnYWNfSm
         0akcWNQRnW0IY4uLoPSFYBNKO4VtAnFJmFn5TPg3al9qumVvJVORMawdCJLpmUx5BUp2
         G9ubxb6P/PuIa3EB/ugAXae7/zf8nJdQ3I9V0=
MIME-Version: 1.0
In-Reply-To: <91f3b2651002282141g183b7575u574978d130fd251e@mail.gmail.com>
References: <91f3b2651002280740y14b1ecdas5ed1f035870bbdea@mail.gmail.com>
	 <e2a35cbc1002281515u555ba243v989063a8e9ce56a4@mail.gmail.com>
	 <91f3b2651002282141g183b7575u574978d130fd251e@mail.gmail.com>
Date: Mon, 1 Mar 2010 10:18:46 +0000
Message-ID: <e2a35cbc1003010218p751893bbkbc7ea24a3bced51b@mail.gmail.com>
Subject: Re: [jr3] Delayed Repository Initialization
From: Guo Du <mrduguo@gmail.com>
To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 1, 2010 at 5:41 AM, Thomas M=FCller <thomas.mueller@day.com> wr=
ote:
> The question is: should Jackrabbit 3 *require* (like now) that the
> credentials for the storage are included in the repository
> configuration? I think for some storage backends it should not require
> that. Instead (only in those cases), it should initialize the

I am not clear what credentials you are refering to and how current
jackrabbit works with backend login. If it's related to storage
backend, it need always store on repository level. Repository
initialisation will need the backend credential to ensure db schema is
there.

Session login credential shouldn't related to backend storage such as
jdbc username/password. Unless we designed to map jcr session user to
jdbc user.

-Guo