Hi Felix,
> Andreas Hartmann schrieb:
>> is it possible to access multiple JCR workspaces via a
>> Sling application?
>
> Basically yes. Your application may grab the Repository (or
> SlingRepository) service from the service registry and login to the
> repository specifying different workspaces to access.
thanks for your answer, it's good to know that accessing multiple
workspaces is possible.
I'd be interested in your opinions about the correct approach to a
staging environment like it is provided by traditional CMS applications.
I see the following options:
Separate workspaces
===================
* Corresponding nodes with same UUID possible
* Updating nodes/subtrees possible
* Question: How are access control settings handled?
Separate areas in a single workspace
====================================
* No corresponding nodes with same UUID possible
* Maintaining access control definitions could be complicated
* Updating nodes/subtrees has to be implemented
Separate areas as child nodes
=============================
* Areas not self-contained
* No direct URI-to-path mapping possible
Labelled versions
=================
* Changes applied immediately, without calling Session.save()
(might be a problem wrt transactions)
* Access control to version history has to be considered
My gut feeling tells me that separate workspaces are the most promising
approach. But I don't know how the access control settings (in this
case, permissions to change properties of particular nodes) are
maintained across workspaces. Would they have to be kept in sync manually?
Is there a general best practise to model this kind of functionality?
Thanks a lot in advance for any hints!
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
