[
https://issues.apache.org/jira/browse/JCRVLT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816441#comment-17816441
]
Konrad Windszus commented on JCRVLT-744:
----------------------------------------
FileVault API is always bound to a JCR session which is always connected to
exactly one workspace. By passing a Session bound to another workspace one can
import/export from arbitrary workspaces already.
I am not sure I get what exactly is missing here...
A content package conceptually can only contain serialized repository contents
from exactly one workspace. Including the workspace name in the content package
is possible, but not sure what should be done in case this content package is
imported into a workspace with a different name.
> Vaults do not handle multi workspace environments
> -------------------------------------------------
>
> Key: JCRVLT-744
> URL: https://issues.apache.org/jira/browse/JCRVLT-744
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Reporter: Jochen
> Priority: Major
>
> The vault properties do not specify, for which workspace the package is.
> All the code implicitly assumes, that there is only one workspace.
> There should be a package property specifying the workspace.
> From a supplied session the switch to another workspace can be done via
> session.getRepository().login(workspaceName)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
