[MAGNOLIA-3151] Constructor of MgnlGroup should be "protected" to allow custom subclasses Created: 19/Mar/10  Updated: 23/Jan/13  Resolved: 19/Mar/10

Status: Closed
Project: Magnolia
Component/s: core, security
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Improvement Priority: Major
Reporter: Benoit Segaert Assignee: Magnolia International
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)
Date of First Response:

 Description   

If you want to extend the Group Manager, you need an access to MgnlGroup constructor but it is limited to his package with the signature:
MgnlGroup(Content groupNode)

Should be
protected MgnlGroup(Content groupNode)

So we could call new MgnlGroup(node) from an extendend Group Manager
It has been extended for User Manager but not yet for Group Manager.



 Comments   
Comment by Magnolia International [ 19/Mar/10 ]

It's indeed inconsistent with MgnlRole and MgnlGroup, so we could do that; additionally, it could help for MAGNOLIA-3147.

Comment by Magnolia International [ 19/Mar/10 ]

done on trunk, cheers.

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