Allow to inherit workspace configuration from repository level template
-----------------------------------------------------------------------

                 Key: JCR-599
                 URL: http://issues.apache.org/jira/browse/JCR-599
             Project: Jackrabbit
          Issue Type: New Feature
          Components: config
    Affects Versions: 0.9, 1.0, 1.0.1, 1.1
            Reporter: Przemo Pakulski
            Priority: Minor


RepositoryConfig file contains section with template for Workspace config. This 
template is used to create new workspace using jackrabbit internal api, and new 
workspace configuration file is created based on this template.

Probably in most scenarios common configuration for all workspaces is used. If 
you need to make some configuration changes then you have to iterate through 
each workspace and edit each config file separately.
It is quit easy task if you are using local file system, but can be hard if 
other file systems are used (for example using DbFileSystem editing blobs in 
database is required).

Our proposal to make some improvement here and allow to inherit workspace 
configuration by reading it from repository level template. Change made in 
repository config file will be reflected auomaticallly in all worskpaces then.

Feature details :
- if workspace.xml file doesn't exists it can be inherited (read and created in 
memory from template), no workspace.xml file must be generated,
- you can still override workspace config by creating workspace.xml file by 
hand, then this file will be used instead of template,
- if required additional parameter 'inheritConfig' can be added with default 
value 'false' to keep current behaviour
and workspace config inheritance will work only if this parameter is set to 
'true'.

We are working on this feature, and we will contribute patch.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to