Hello
Indeed I had seen this problem regarding Jackrabbit, it still exists even if
a correction was made by https://issues.apache.org/jira/browse/JCR-3440.
Thank you
--
View this message in context:
http://apache-sling.73963.n3.nabble.com/Lock-on-LOCAL-REVISONS-table-tp4068204p4068221.html
Hello,
Currently when you get content through the json extension, it contains
protected properties ("jcr:created", "jcr:createdBy") and permissions nodes.
The protected properties prevent the JSON to be immediately reimported in
another repository, and for what I see here [1] permissions are not
Hi,
On Tue, Nov 29, 2016 at 4:39 PM, JMR wrote:
> ...Do you know this kind of problem and how to solve it?...
Maybe someone here can help (I can't) but this looks more like a pure
Jackrabbit problem, maybe related to
https://issues.apache.org/jira/browse/JCR-3738 ?
We use Apache Sling 7 (jackrabbit-core 2.6.5) with 2 clusters on a WAS
WebSphere Platform 8.5 (Java version (IBM) 1.6.0).
The configuration of the Jackrabbit repository (uses ORACLE database) is as
follows:
http://jackrabbit.apache.org/dtd/repository-2.0.dtd;>
Thank you Robert for these information,
>From quick tests, backuping the Sling home directory (we're using Sling war
in JBoss and not the launchpad), changing DB connexion information in every
Jackrabbit config file and then reloading a DB dump seems to work.
Regards,
Guillaume
On Sat, Oct 15,