2011/9/5 Grégory Joseph <[email protected]> > > On 05 Sep 2011, at 01:58, Danilo Ghirardelli wrote: > > - even in Jackrabbit 2, is there a simple way to change connection data? I > mean, if I change db password or connection details, the only way is still > to search and change a dozen of xml files in the repo folder, or at least so > it seemed to me. Is there a way to use a property file or at least change > the original repo file and have this part of the configuration adapted > automatically? Even using system properties (which I don't particularly like > in environments that may have more than one instance), they seem to be used > just the first time... > > Either way, you should use a datasource. The password is then nowhere to be > found except in your server's declaration of the DS. Additional benefit is > that you can use the same config file for multiple instances, even if the db > url/user/pass are different. >
just an additional note: also if you use a datasource declared directly in the jackrabbit config file should be fine, there is no need for using a jndi datasource. That part of the configuration is not copied in workspace folders so you will be able to change it in the file deployed with the webapp without problems. > - am I the only one that got this particular issue? > > https://issues.apache.org/jira/browse/JCR-2892 > yes, we definitively did... different results as you can see from Manuel comment on the jackrabbit jira, but for the same reason. For us that change ended up in a performance degradation (50x slower) and we had to patch ConnectionHelper. Everything was fine from jackrabbit 2.0 to 2.2.1, only later versions have this bug. fabrizio ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
