jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martijn Hendriks <marti...@gx.nl>
Subject RE: Jackrabbit fails to start if database user is not schema owner
Date Fri, 13 Mar 2009 08:58:34 GMT
That's indeed what is happening and what makes Jackrabbit fail to start. The case is, however,
that for this particular deployment it is preferred to don't give those rights to the jackrabbit
user. I can think of a Jackrabbit patch that solves this issue but that affects the semantics
of the repository.xml and quite some code with some risk for regression. I realize that this
is a corner case and I am wondering whether we should support this in Jackrabbit or not.

Best regards,
Van: Alexander Klimetschek [aklimets@day.com]
Verzonden: vrijdag 13 maart 2009 0:47
Aan: dev@jackrabbit.apache.org
Onderwerp: Re: Jackrabbit fails to start if database user is not schema owner

On Thu, Mar 12, 2009 at 2:40 PM, Martijn Hendriks <martijnh@gx.nl> wrote:
> The tables already existed. The testcase is this:
> * Start Jackrabbit the regular way which you describe (Jackrabbit autocreates the tables).
> * Stop Jackrabbit
> * Change the user credentials in the repository.xml to those of a user with only data
manipulation rights.
> * Start Jackrabbit again -> this does not work.
> The check whether the tables exist in the checkSchema method in this case finds that
the schema does not yet exist and it tries to create it which fails.

Then it seems that the user has no rights to look at the metadata (in
jdbc terms) and "see" that the table exists. Maybe you can give him
those rights.


Alexander Klimetschek

View raw message