[MAGNOLIA-5934] API to dynamically register workspace Created: 29/Sep/14  Updated: 21/Oct/14  Resolved: 01/Oct/14

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

Type: Improvement Priority: Neutral
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File DefaultRepositoryManager$1.class     File DefaultRepositoryManager.class     File RepositoryManager.class     Text File createWorkspace.patch    
Issue Links:
dependency
is depended upon by MAGNOLIA-5939 Expose method for workspace creation ... Closed
is depended upon by MGNLGROOVY-122 Sample script to register app dynamic... Closed
Template:
Patch included:
Yes
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   

Currently the only way to register new workspace is to define it in module descriptor and let ModuleManagerImpl handle the registration at startup of Magnolia in its private methods.
It would seem more appropriate to move this code to RepositoryManager or to Provider as need to register new workspace is not specific to ModuleManagerImpl.
This change is specially relevant since deprecation of Data module as it prevents creation and registration of new workspace and content apps connected to them without restart of Magnolia.



 Comments   
Comment by Jan Haderka [ 01/Oct/14 ]

Committed only DefaultRepositoryManager part and related test. The change in interface as well as change in ModuleManagerImpl to use new method will be committed in subsequent ticket for 5.4 only (assuming currently committed part will pass review).

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