[MAGNOLIA-6290] Unify code for handling with mgnlVersion and mgnlSystem workspaces Created: 08/Jul/15  Updated: 17/Mar/21  Resolved: 17/Mar/21

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Milan Divilek Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: backlog541
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)

 Description   

MAGNOLIA-5975 brings support for transactional activation and versioning on multiple repositories. This name pattern <repositoryId>-<workspaceId> is used for for mgnlSystem and mgnlVersion workspaces, because it's needed to distinguish which mgnlSystem and mgnlVersion workspace belongs to which repository.

We should unify code for working with mgnlSystem and mgnlVersion workspaces. Get rid of usage of constants for those workspaces (info.magnolia.repository.RepositoryConstants#VERSION_STORE, info.magnolia.cms.beans.config.ContentRepository#VERSION_STORE, info.magnolia.cms.core.version.BaseVersionManager#VERSION_WORKSPACE, info.magnolia.repository.RepositoryConstants#SYSTEM, etc.) and introduce util methods for working with mgnlSystem and mgnlVersion workspaces (such a info.magnolia.jcr.util.VersionUtil#getVersionWorkspaceForNode)


Generated at Mon Feb 12 04:13:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.