[
https://issues.apache.org/jira/browse/JCR-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638091#action_12638091
]
Jukka Zitting commented on JCR-1677:
------------------------------------
> why not apply the patch as it is for 1.5 and fix it better in a later version?
I don't think that the current patch is a technically sound solution to this
issue. Sure, it works in specific circumstances but it also fails miserably in
others. There is also no reasonably backwards-compatible way of upgrading this
feature to something better in future releases, so it would essentially be a
one-off hack.
Implementing this feature properly shouldn't be too hard. See JCR-699 for an
example on how this was done for node type registration.
> Allow workspace creation over cluster
> -------------------------------------
>
> Key: JCR-1677
> URL: https://issues.apache.org/jira/browse/JCR-1677
> Project: Jackrabbit
> Issue Type: Improvement
> Components: clustering, jackrabbit-core
> Reporter: Matej Knopp
> Attachments: patch-1677-1.txt, patch-1677-2.txt
>
>
> When workspace is created on cluster node A and then node added to that
> workspace, the proper event is sent to the journal, but other cluster nodes
> are not able to process it because they don't have the workspace.
> It would be nice to have a configuration option for the cluster to create
> such workspace automatically (instead of just logging an error)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
