You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by "PREVOSTO, Laurent" <la...@sfr.com> on 2011/01/23 19:38:52 UTC
configFile vs repository.xml
Sorry gentlemen, as it may be a FAQ...
but, once for all, i would like to know how things work regarding jackrabbit (we use 1.6.2) confilg files :
We are using jboss, hence have jcr-ds.xml with the following line :
<config-property name="homeDir" type="java.lang.String">/foobar/myapp/data/jcr</config-property>
<config-property name="configFile" type="java.lang.String">classpath:myapp/repository-val.xml</config-property>
in the conf dir of jboss lies a myapp/repository-val.xml file with the complete configuration
which defines :
<Workspaces rootPath="${rep.home}/workspaces" defaultWorkspace="default"/>
and
<Versioning rootPath="${rep.home}/version">
And of course there is another config file there :
/foobar/myapp/data/jcr/workspaces/default/workspace.xml
>From the documentation, it looks like the actual configuration (persistenceManager, datastore, etc.) should come from /foobar/myapp/data/jcr/workspaces/default/workspace.xml (which first starts as a copy of the main one - repository-val.xml).
But guys here tell me that modifying there main one (repository-val.xml) works fine if we want to modify PM's db credentials for instance...
All this is quite confusing. Where lies the truth ?
Or are there properties that come from the main repository.xml and others that can be overloaded in workspace.xml ?
I am afraid that sometimes people modify workspace.xml and sometimes repository-val.xml and consequently, nobody knows jackrabbit's exact configuration... which is somewhat scary :-)
Thanx for answers.
Regards,
Laurent
RE: RE : configFile vs repository.xml
Posted by "PREVOSTO, Laurent" <la...@sfr.com>.
Unfortunately,
It does not seem to work.
Looks like the dot turned into an underscore.
I end up with such errors :
Failed to create session: Cannot instantiate persistence manager org.apache.jackrab
bit.core.persistence.bundle.OraclePersistenceManager: Schema generation error: Issuing statement: create unique index MYSCHEMA_J
CR_DEFAULT_BUNDLE_IDX on MYSCHEMA_JCR_DEFAULT_BUNDLE (NODE_ID)
I tried to escape the dot but it didn't work...
Regards,
Laurent
-----Message d'origine-----
De : Alexander Klimetschek [mailto:aklimets@adobe.com]
Envoyé : mardi 25 janvier 2011 14:12
À : users@jackrabbit.apache.org
Objet : Re: RE : configFile vs repository.xml
On 25.01.11 13:24, "PREVOSTO, Laurent" <la...@sfr.com> wrote:
>I don't think so,
>As i understand it, it is used as a prefix to build the names of the
>Jackrabbit tables and indexes.
>
>Ex :
>
>JCR_MYPREFIX_BINVAL
>JCR_MYPREFIX_BUNDLES
>
>But it is does not look like the Oracle Schema.
If I am not mistaken, you can specify the schema in the table names using
"<schema>.<table>". Thus a schemaObjectPrefix such as "myschema.jcr_"
could do the trick.
Regards,
Alex
--
Alexander Klimetschek
Developer // Adobe (Day) // Berlin - Basel
Re: RE : configFile vs repository.xml
Posted by Alexander Klimetschek <ak...@adobe.com>.
On 25.01.11 13:24, "PREVOSTO, Laurent" <la...@sfr.com> wrote:
>I don't think so,
>As i understand it, it is used as a prefix to build the names of the
>Jackrabbit tables and indexes.
>
>Ex :
>
>JCR_MYPREFIX_BINVAL
>JCR_MYPREFIX_BUNDLES
>
>But it is does not look like the Oracle Schema.
If I am not mistaken, you can specify the schema in the table names using
"<schema>.<table>". Thus a schemaObjectPrefix such as "myschema.jcr_"
could do the trick.
Regards,
Alex
--
Alexander Klimetschek
Developer // Adobe (Day) // Berlin - Basel
RE: RE : configFile vs repository.xml
Posted by "PREVOSTO, Laurent" <la...@sfr.com>.
I don't think so,
As i understand it, it is used as a prefix to build the names of the Jackrabbit tables and indexes.
Ex :
JCR_MYPREFIX_BINVAL
JCR_MYPREFIX_BUNDLES
But it is does not look like the Oracle Schema.
Regards,
Lauretn
-----Message d'origine-----
De : Seidel. Robert [mailto:Robert.Seidel@aeb.de]
Envoyé : mardi 25 janvier 2011 09:22
À : users@jackrabbit.apache.org
Objet : AW: RE : configFile vs repository.xml
Hi Laurent,
schemaObjectPrefix should do the job.
/**
* Sets the schema object prefix. This string is used to prefix all schema
* objects, like tables and indexes. this is useful, if several persistence
* managers use the same database.
*
* @param schemaObjectPrefix the prefix for schema objects.
*/
Regards, Robert
-----Ursprüngliche Nachricht-----
Von: PREVOSTO, Laurent [mailto:laurent.prevosto@sfr.com]
Gesendet: Montag, 24. Januar 2011 21:57
An: users@jackrabbit.apache.org
Betreff: RE: RE : configFile vs repository.xml
Now that i eventually understood, here comes the final question :
With the Oracle BundleDB PM, is there a way to specify a schema for the jackrabbit tables (ie : not the schema that matches the oracle connection login).
Regards,
Laurent
-----Message d'origine-----
De : Seidel. Robert [mailto:Robert.Seidel@aeb.de]
Envoyé : lundi 24 janvier 2011 15:34
À : users@jackrabbit.apache.org
Objet : AW: RE : configFile vs repository.xml
Hi Laurent,
yes you are - the workspace settings in repository.xml are just default values if there is no existing workspace.xml. However the workspace.xmls will be created at the first access.
Regards, Robert
-----Ursprüngliche Nachricht-----
Von: PREVOSTO, Laurent [mailto:laurent.prevosto@sfr.com]
Gesendet: Montag, 24. Januar 2011 14:13
An: users@jackrabbit.apache.org
Betreff: RE: RE : configFile vs repository.xml
Hi Jukka,
I had read this documentation.
But just to make it clear, the rule should be :
If I want to modify something regarding workspace configuration (in my case, the way you connect to the PM database), you should :
1. modify repository.xml (in case you create new workspaces)
2. modify existings workspace.xml
(1) only would be useless.
Am I right ?
Regards,
Laurent
-----Message d'origine-----
De : Jukka Zitting [mailto:jzitting@adobe.com]
Envoyé : lundi 24 janvier 2011 12:59
À : users@jackrabbit.apache.org
Objet : Re: RE : configFile vs repository.xml
Hi,
On 23.01.2011 22:45, PREVOSTO, Laurent wrote:
> But does anybody know which are repository level and workspace level
> configurations ? Or is it documented somewhere ?
See http://jackrabbit.apache.org/jackrabbit-configuration.html
--
Jukka Zitting
AW: RE : configFile vs repository.xml
Posted by "Seidel. Robert" <Ro...@aeb.de>.
Hi Laurent,
schemaObjectPrefix should do the job.
/**
* Sets the schema object prefix. This string is used to prefix all schema
* objects, like tables and indexes. this is useful, if several persistence
* managers use the same database.
*
* @param schemaObjectPrefix the prefix for schema objects.
*/
Regards, Robert
-----Ursprüngliche Nachricht-----
Von: PREVOSTO, Laurent [mailto:laurent.prevosto@sfr.com]
Gesendet: Montag, 24. Januar 2011 21:57
An: users@jackrabbit.apache.org
Betreff: RE: RE : configFile vs repository.xml
Now that i eventually understood, here comes the final question :
With the Oracle BundleDB PM, is there a way to specify a schema for the jackrabbit tables (ie : not the schema that matches the oracle connection login).
Regards,
Laurent
-----Message d'origine-----
De : Seidel. Robert [mailto:Robert.Seidel@aeb.de]
Envoyé : lundi 24 janvier 2011 15:34
À : users@jackrabbit.apache.org
Objet : AW: RE : configFile vs repository.xml
Hi Laurent,
yes you are - the workspace settings in repository.xml are just default values if there is no existing workspace.xml. However the workspace.xmls will be created at the first access.
Regards, Robert
-----Ursprüngliche Nachricht-----
Von: PREVOSTO, Laurent [mailto:laurent.prevosto@sfr.com]
Gesendet: Montag, 24. Januar 2011 14:13
An: users@jackrabbit.apache.org
Betreff: RE: RE : configFile vs repository.xml
Hi Jukka,
I had read this documentation.
But just to make it clear, the rule should be :
If I want to modify something regarding workspace configuration (in my case, the way you connect to the PM database), you should :
1. modify repository.xml (in case you create new workspaces)
2. modify existings workspace.xml
(1) only would be useless.
Am I right ?
Regards,
Laurent
-----Message d'origine-----
De : Jukka Zitting [mailto:jzitting@adobe.com]
Envoyé : lundi 24 janvier 2011 12:59
À : users@jackrabbit.apache.org
Objet : Re: RE : configFile vs repository.xml
Hi,
On 23.01.2011 22:45, PREVOSTO, Laurent wrote:
> But does anybody know which are repository level and workspace level
> configurations ? Or is it documented somewhere ?
See http://jackrabbit.apache.org/jackrabbit-configuration.html
--
Jukka Zitting
RE: RE : configFile vs repository.xml
Posted by "PREVOSTO, Laurent" <la...@sfr.com>.
Now that i eventually understood, here comes the final question :
With the Oracle BundleDB PM, is there a way to specify a schema for the jackrabbit tables (ie : not the schema that matches the oracle connection login).
Regards,
Laurent
-----Message d'origine-----
De : Seidel. Robert [mailto:Robert.Seidel@aeb.de]
Envoyé : lundi 24 janvier 2011 15:34
À : users@jackrabbit.apache.org
Objet : AW: RE : configFile vs repository.xml
Hi Laurent,
yes you are - the workspace settings in repository.xml are just default values if there is no existing workspace.xml. However the workspace.xmls will be created at the first access.
Regards, Robert
-----Ursprüngliche Nachricht-----
Von: PREVOSTO, Laurent [mailto:laurent.prevosto@sfr.com]
Gesendet: Montag, 24. Januar 2011 14:13
An: users@jackrabbit.apache.org
Betreff: RE: RE : configFile vs repository.xml
Hi Jukka,
I had read this documentation.
But just to make it clear, the rule should be :
If I want to modify something regarding workspace configuration (in my case, the way you connect to the PM database), you should :
1. modify repository.xml (in case you create new workspaces)
2. modify existings workspace.xml
(1) only would be useless.
Am I right ?
Regards,
Laurent
-----Message d'origine-----
De : Jukka Zitting [mailto:jzitting@adobe.com]
Envoyé : lundi 24 janvier 2011 12:59
À : users@jackrabbit.apache.org
Objet : Re: RE : configFile vs repository.xml
Hi,
On 23.01.2011 22:45, PREVOSTO, Laurent wrote:
> But does anybody know which are repository level and workspace level
> configurations ? Or is it documented somewhere ?
See http://jackrabbit.apache.org/jackrabbit-configuration.html
--
Jukka Zitting
AW: RE : configFile vs repository.xml
Posted by "Seidel. Robert" <Ro...@aeb.de>.
Hi Laurent,
yes you are - the workspace settings in repository.xml are just default values if there is no existing workspace.xml. However the workspace.xmls will be created at the first access.
Regards, Robert
-----Ursprüngliche Nachricht-----
Von: PREVOSTO, Laurent [mailto:laurent.prevosto@sfr.com]
Gesendet: Montag, 24. Januar 2011 14:13
An: users@jackrabbit.apache.org
Betreff: RE: RE : configFile vs repository.xml
Hi Jukka,
I had read this documentation.
But just to make it clear, the rule should be :
If I want to modify something regarding workspace configuration (in my case, the way you connect to the PM database), you should :
1. modify repository.xml (in case you create new workspaces)
2. modify existings workspace.xml
(1) only would be useless.
Am I right ?
Regards,
Laurent
-----Message d'origine-----
De : Jukka Zitting [mailto:jzitting@adobe.com]
Envoyé : lundi 24 janvier 2011 12:59
À : users@jackrabbit.apache.org
Objet : Re: RE : configFile vs repository.xml
Hi,
On 23.01.2011 22:45, PREVOSTO, Laurent wrote:
> But does anybody know which are repository level and workspace level
> configurations ? Or is it documented somewhere ?
See http://jackrabbit.apache.org/jackrabbit-configuration.html
--
Jukka Zitting
RE: RE : configFile vs repository.xml
Posted by "PREVOSTO, Laurent" <la...@sfr.com>.
Hi Jukka,
I had read this documentation.
But just to make it clear, the rule should be :
If I want to modify something regarding workspace configuration (in my case, the way you connect to the PM database), you should :
1. modify repository.xml (in case you create new workspaces)
2. modify existings workspace.xml
(1) only would be useless.
Am I right ?
Regards,
Laurent
-----Message d'origine-----
De : Jukka Zitting [mailto:jzitting@adobe.com]
Envoyé : lundi 24 janvier 2011 12:59
À : users@jackrabbit.apache.org
Objet : Re: RE : configFile vs repository.xml
Hi,
On 23.01.2011 22:45, PREVOSTO, Laurent wrote:
> But does anybody know which are repository level and workspace level
> configurations ? Or is it documented somewhere ?
See http://jackrabbit.apache.org/jackrabbit-configuration.html
--
Jukka Zitting
Re: RE : configFile vs repository.xml
Posted by Jukka Zitting <jz...@adobe.com>.
Hi,
On 23.01.2011 22:45, PREVOSTO, Laurent wrote:
> But does anybody know which are repository level and workspace level
> configurations ? Or is it documented somewhere ?
See http://jackrabbit.apache.org/jackrabbit-configuration.html
--
Jukka Zitting
RE : configFile vs repository.xml
Posted by "PREVOSTO, Laurent" <la...@sfr.com>.
I see...
But does anybody know which are repository level and workspace level configurations ?
Or is it documented somewhere ?
For instance PM credentials, ISMLocking, etc...
I am afraid we think we have configured something... but actually not.
regards,
Laurent
________________________________________
De : justinedelson@gmail.com [justinedelson@gmail.com] de la part de Justin Edelson [justin@justinedelson.com]
Date d'envoi : dimanche 23 janvier 2011 20:20
À : users@jackrabbit.apache.org
Objet : Re: configFile vs repository.xml
On Sun, Jan 23, 2011 at 1:38 PM, PREVOSTO, Laurent <laurent.prevosto@sfr.com
> wrote:
>
> From the documentation, it looks like the actual configuration
> (persistenceManager, datastore, etc.) should come from
> /foobar/myapp/data/jcr/workspaces/default/workspace.xml (which first starts
> as a copy of the main one - repository-val.xml).
> But guys here tell me that modifying there main one (repository-val.xml)
> works fine if we want to modify PM's db credentials for instance...
>
>
Keep in mind that there may be credentials in repository.xml in the
configuration of repository-level objects such as the FileSystem or
DataStore.
Re: configFile vs repository.xml
Posted by Justin Edelson <ju...@justinedelson.com>.
On Sun, Jan 23, 2011 at 1:38 PM, PREVOSTO, Laurent <laurent.prevosto@sfr.com
> wrote:
>
> From the documentation, it looks like the actual configuration
> (persistenceManager, datastore, etc.) should come from
> /foobar/myapp/data/jcr/workspaces/default/workspace.xml (which first starts
> as a copy of the main one - repository-val.xml).
> But guys here tell me that modifying there main one (repository-val.xml)
> works fine if we want to modify PM's db credentials for instance...
>
>
Keep in mind that there may be credentials in repository.xml in the
configuration of repository-level objects such as the FileSystem or
DataStore.