[MAGNOLIA-1270] ModuleUtil does not check for existing workspace mapping on register Created: 14/Dec/06  Updated: 23/Jan/13  Resolved: 14/Dec/06

Status: Closed
Project: Magnolia
Component/s: build
Affects Version/s: 3.0.1
Fix Version/s: 3.0.5

Type: Bug Priority: Minor
Reporter: Sameer Charles Assignee: Sameer Charles
Resolution: Fixed Votes: 0
Labels: None
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

problem occur when you try to share single JCR repository between multiple magnolia instances.

  • repositories.xml allows you to configure workspace name mapping to give a repository wide unique name to the workspaces
  • all works fine but on bootstrap when module register itself, it fails to recognize existing repository mapping and alwaqys try to add a new workspace
    with the name defined in META-INF module descriptor


 Comments   
Comment by Sameer Charles [ 14/Dec/06 ]

fixed on svn

  • module util does not create workspace if mapping already exist
Generated at Mon Feb 12 03:25:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.