This patch adds the possibility to read (but not write) the Cluster JOURNAL from a different source than the rest of the cluster information. This makes it possible to setup a master/slave DB setup, where everything cluster related is read from the slave, but writes to the master. It reads the actual data also from the slave and assumes that this jackrabbit instance never does any writes (except for updating the cluster index position in the DB). We have to read the Cluster Journal from the slave to guarantee a consistent state
I didn't write any tests yet, if you can point me, where I should add them, I'll gladly do them.
Would be great, if we could integrate that in any of the future Jackrabbit releases.
It's of course fully backwards compatible, nothing changes, if you don't sepcify