[
https://issues.apache.org/jira/browse/JCR-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638115#action_12638115
]
Jukka Zitting commented on JCR-1677:
------------------------------------
> not sure what is not technically sound about this.
For example it conflicts with the JackrabbitWorkspace.createWorkspace(String,
InputSource) method (see [1]).
The reason why the <Workspace/> element in repository.xml is just the default
template is to allow different workspace to be configured differently. Such
non-uniform setups are actually fairly common (at least in deployments that I
see).
Of course the patch makes such clustered workspace creation optional, so one
could argue that people with such non-uniform setups should just not enable
this feature. But since implementing this feature properly for all sorts of
setups is not really that much harder (the patch for JCR-699 was only twice as
big as the current patch here), I would rather not opt for a partial fix that
we'd then need to keep supporting for backwards compatibility reasons.
> i am curious why you removed 1.5 fix version
See the 1.5 release plan updates on [EMAIL PROTECTED] I plan to move forward
with 1.5 already within the next few weeks and would rather postpone unfinished
issues to 1.6.
I'd like have this feature included already in 1.5, but only if we do it along
the lines of JCR-699.
[1]
http://jackrabbit.apache.org/api/1.4/org/apache/jackrabbit/api/JackrabbitWorkspace.html#createWorkspace(java.lang.String,
org.xml.sax.InputSource)
> 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.
