[
https://issues.apache.org/jira/browse/JCRVLT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816544#comment-17816544
]
Konrad Windszus commented on JCRVLT-744:
----------------------------------------
I think the issue with the session is not only with
{{JcrPackageManager.assemble(....)}} but probably also
{{JcrPackageManager.extract(...)}} and most methods in {{JcrPackage}} (all
currently just use the session of the package definition node which might be
located in a different workspace). Not sure whether fixing the legacy
JcrPackage/-Manager makes sense or whether just investing into JCRVLT-504 is
more reasonable.
> 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)
