Hi Justin,
thanks a lot for your swift response.
> I think the subject of this thread is slightly misleading... it really
> should be "scripts should be resolved from the same workspace as
> resources". Which is essentially the summary of SLING-1446.
ahhh ok, that definitely makes more sense...
>> They are not for separating things out, like user A has a workspace
>> and user B has
>> a workspace, they are also not for separation by type.
> I have to stop you there. user-specific workspaces seem like a perfectly
> legitimiate use of workspaces IF those users are editing the same
> content tree.
Agreed. Which would make in turn use of merge() update() and clone() ;)
> Imagine four workspaces:
> 1) user1
> 2) user2
> 3) trunk
> 4) publish
> A node is created in user1 at /content/index, then clone() is called in
> trunk [i.e. clone("user1", "/content/index", "/content/index", false)].
> The node is then cloned into user2 [i.e. clone("trunk",
> "/content/index", "/content/index", false)]. User2 makes some changes in
> their workspace, saves, and then updates the node in trunk
> [node.update("user2")]. Finally, the node is clone from trunk to publish
> and is user-facing.
> The key point I've understood about workspaces and their appropriate use
> is that workspaces are supposed to represent the same content tree.
> Having private working copies doesn't seem to violate this.
Absolutely. I agree with you. Maybe I should clarify that in the wiki...
I was mostly referring to a usecase of multi-tenancy that people sometime
mistake as a good usecase for workspaces.
> By the by, something to consider for JCR 3 is that clone/update/merge
> all operate from the perspective of the "target" workspace (i.e. the
> workspace being cloned into, updated, merged). For promotion workflows,
> I believe corresponding methods called from the source workspace/session
> would be more natural, similar to how "git push" works.
Hmm... Good point. Maybe even JCR 2.1.
I think the issue is that to make modification in a workspace other than the
one that you have a session to is something that we lack some machinery
for...
thanks for the follow-up.
regards,
david
