Jackrabbit configuration

[Brian Thompson <el...@gmail.com>]

Greetings,

I'm using Jackrabbit as part of a web app that will be deployed to a new
server later this week.  In development, we've been using using database
filesystem and database persistence.

One of the requirements of deploying the app is that we connect to a new
database for production.  I've identified all the places where the DB
connection string is stored (several places in jackrabbit-repository.xml,
plus two places in workspace.xml for each workspace the app is using), so
changing that won't be a problem.

However, it's a pain to go through and manually synch all those connection
strings.  I'd really like to pull out the connection string into a property
like ${rep.home} or ${wsp.home} that Jackrabbit makes available in the
config files.  I've already tried adding the DB connection string to a
.properties file in my classpath, but it didn't work - on startup, the
application threw:

org.apache.jackrabbit.core.config.ConfigurationException: Replacement not
found for ${jcr.dbstring}.

Is there a mechanism for centralizing configuration that I'm not aware of?

Thanks!

-Brian

Re: Jackrabbit configuration

[Brian Thompson <el...@gmail.com>]

Thanks!  I'll take a look at it :)

-Brian

On 4/23/07, Miro Walker <mi...@gmail.com> wrote:
>
> Hi Brian,
>
> See this issue: https://issues.apache.org/jira/browse/JCR-599 for a
> proposed solution to this, namely to allow inheritance of workspace
> config from the repository config template.
>
> This supports the use cases where a single database is used to store
> all workspaces, so there is no point in being able to configure each
> workspace independently. There's a patch attached to the issue that
> allows this to be turned on (although it's against an older jackrabbit
> version, so it's probable it'll need updating to work against the
> current version).
>
> Unfortunately at the time the patch was proposed there was no interest
> from the community, so it was never committed. Perhaps if you vote for
> the issue, someone will look at it again? :-)
>
> Cheers,
>
> Miro
>

Re: Jackrabbit configuration

[Miro Walker <mi...@gmail.com>]

Hi Brian,

See this issue: https://issues.apache.org/jira/browse/JCR-599 for a
proposed solution to this, namely to allow inheritance of workspace
config from the repository config template.

This supports the use cases where a single database is used to store
all workspaces, so there is no point in being able to configure each
workspace independently. There's a patch attached to the issue that
allows this to be turned on (although it's against an older jackrabbit
version, so it's probable it'll need updating to work against the
current version).

Unfortunately at the time the patch was proposed there was no interest
from the community, so it was never committed. Perhaps if you vote for
the issue, someone will look at it again? :-)

Cheers,

Miro