[
https://issues.apache.org/jira/browse/JCR-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominique Pfister resolved JCR-702.
-----------------------------------
Resolution: Fixed
Added a new journal implementation that remembers changes in the database.
Verified with the following databases: Derby Network Server, H2 and Oracle.
Sample cluster configuration looks as follows (Derby):
<Cluster>
<Journal class="org.apache.jackrabbit.core.cluster.DatabaseJournal">
<param name="driver" value="org.apache.derby.jdbc.ClientDriver"/>
<param name="url"
value="jdbc:derby://localhost:1527/jackrabbit;create=true"/>
</Journal>
</Cluster>
Further configuration details are available in DatabaseJournal's javadoc.
Fixed in revision 495240.
> Allow database as backend for clustering
> ----------------------------------------
>
> Key: JCR-702
> URL: https://issues.apache.org/jira/browse/JCR-702
> Project: Jackrabbit
> Issue Type: New Feature
> Components: core
> Affects Versions: 1.2
> Reporter: Dominique Pfister
> Assigned To: Dominique Pfister
>
> Currently, clustering (see JCR-623) uses a shared file system folder in order
> to store modifications and synchronize all nodes in the cluster.
> Alternatively, a database backend should be available.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
