[
https://issues.apache.org/jira/browse/JCR-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834843#action_12834843
]
Daniel Hopper commented on JCR-2003:
------------------------------------
Thanks for the prompt response.
If that is the case how exactly should one connect be connecting to Jackrabbit
in a cluster if the various SPI don't support all the features?
So for instance lets say we have a 4 node cluster of Jackrabbit servers. Our
App servers were connecting to the cluster via RMI currently (application in
prototype phase). We were looking to switch to DavEx but it appears to not
implement all the various features necessary.
What way should we be connecting to JCR then via the SPI?
Regards
> JCR2SPI / SPI: Add support for JCR 2.0
> ---------------------------------------
>
> Key: JCR-2003
> URL: https://issues.apache.org/jira/browse/JCR-2003
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-jcr2spi, jackrabbit-spi,
> jackrabbit-spi-commons, jackrabbit-spi2dav, jackrabbit-spi2jcr, JCR 2.0,
> sandbox
> Reporter: angela
>
> Container issue to keep track of any changes made to JCR2SPI / SPI and
> implementations that adds functionality or changes existing functionality
> based on requirements defined in JSR 283.
> According to a recent discussion with david we will most probably do this
> step by step and according to our needs / resources available.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
