jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guo Du <mrdu...@gmail.com>
Subject Re: [jr3] Delayed Repository Initialization
Date Mon, 01 Mar 2010 11:12:53 GMT
On Mon, Mar 1, 2010 at 10:50 AM, Thomas Müller <thomas.mueller@day.com> wrote:
> Currently, Jackrabbit requires to be able to create a database
> connection when initializing.
I was thought like this too :)

> It depends on what you mean with "repository level". It doesn't make
> sense to store the user name and password of the database inside the
> database (I hope you agree :-)
I mean repository configuration, which will pass to repository
instance during initialisation, not repository instance itself.

> I would like to make repository.xml optional. To do that, the user
> String url = "...?user=sa&password=xyz";
> Session session = rep.login(new SimpleCredentials("sa", "xyz".toCharArray()));

I am not sure it's good practice to associated session user with
repository storage (by default I refer to jdbc database server) user.
Because different session user may have different privilege on
database server, while repository doesn't recognise the difference
(e.g. reader user is not allowed to update on db and will fail to
create schema and update).

We are trying to agree on to associate the storage username/password
with repository or session, right?

Where to put the username/password is another discussion, via
repository xml, url, factory, osgi or any of them.


View raw message