[PUBLISHING-10] Ad-hoc Registration of workspace to subscribers Created: 08/Feb/17  Updated: 29/Mar/22  Resolved: 18/Sep/17

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

Type: Task Priority: Neutral
Reporter: Espen Jervidalo Assignee: Jaroslav Simak
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLCT-2 Allow ad-hoc subscription of created ... Closed
relates to MAGNOLIA-6982 NPE when workspace subscription setup... Closed
supersession
is superseded by MGNLCT-2 Allow ad-hoc subscription of created ... Closed
is superseded by PUBLISHING-2 Implement publishing-sender Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Activation rewrite
Story Points: 2
Team: Nucleus

 Description   

We need to register workspaces without having to touch any JCR configuration. One missing piece is configuration of the workspace-subscriptions under /server/activation/subscribers/xy/subscriptions.

The subscription is automatically set up during installation of the module in info.magnolia.module.delta.SetupModuleRepositoriesTask#subscribeRepository

Whether the subscription (adding the node to the subscribers) is performed during install or not is voter-based. The voting mechanism is not intended (but used) for deciding whether the subscription should be performed or not, it is relevant for voting for the best subscription during an activation. This is weird and should be simplified.

The idea so far is to configure the workspaces you do not want to subscribe and not as today to add those that should be subscribed.

Further notes:

  • Introduce new API and replace usage of core-interfaces in info.magnolia.cms.exchange
  • Please clean up the usage of repository in the code where workspace is meant, at least where possible.


 Comments   
Comment by Jan Haderka [ 17/Jul/17 ]

MCTP-2 solves this issue only for apps/workspaces created via light modules, however it does nothing for workspaces created dynamically by code or install tasks.

Comment by Jaroslav Simak [ 18/Sep/17 ]

Solved by MGNLACTIVATION-161.

Generated at Mon Feb 12 10:34:31 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.