It's not officially supported by Magnolia right now, I know, but I tried
to use JackRabbit 2 on a small Magnolia project, just to be forward
compatible (and also because I was curious).
Everything worked fine (except one thing I'll say later), APIs are
compatible and everything is good now. But I have a couple of questions,
maybe you have already answered them with the development of Magnolia 5:
- 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...
- am I the only one that got this particular issue?
https://issues.apache.org/jira/browse/JCR-2892
I know I'm quite unlucky with my corner cases, but this setup seems
quite common (oracle db + clustering)... Just to see whether it's
something special that is triggering the problem in my system or the
problem is just in Jackrabbit.
Regards, Danilo.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
