[MAGNOLIA-1592] Revive Subscriber class for 3.1 (deprecate it) Created: 13/Jun/07  Updated: 23/Jan/13  Resolved: 31/Oct/07

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

Type: Task Priority: Blocker
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File Subscriber.java    
Issue Links:
relation
is related to MAGNOLIA-1546 Subscribers with custom contexts are ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

info.magnolia.cms.beans.config.Subscriber was removed for MAGNOLIA-1546 in r9626; Since it's potentially used by custom modules/projects (it was used in DMSAdminTreeConfig for instance), we should revive it (as deprecated) for 3.1. Delegation to the new subscription component seems reasonably possible.



 Comments   
Comment by Oliver Lietz [ 14/Jun/07 ]

I used it as follows:

if (Server.isAdmin() || Subscriber.isSubscribersEnabled())

{ tree.addColumn(activationState); }

There should be a single property or method to check if we want so show activationState.

Comment by Magnolia International [ 31/Oct/07 ]

Here's a skeleton, should anyone be ready to take up on this task.

Comment by Magnolia International [ 31/Oct/07 ]

done.
Some methods probably return irrelevant results. Added deprecation warning messages.

Comment by Magnolia International [ 31/Oct/07 ]

Oliver: now you can simply do ActivationManagerFactory.getActivationManager().hasAnyActiveSubscriber() instead.
Admittedly this is pretty verbose, so we could add a(nother) utility method in TreeColumn for instance.

Generated at Mon Feb 12 03:28:24 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.