[MAGNOLIA-316] HierarchyManager can become immutable with respect to most of its fields. Created: 16/Mar/05 Updated: 25/Nov/13 Resolved: 25/Nov/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 2.1 Final, 3.0.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | David Bullock | Assignee: | Sameer Charles |
| Resolution: | Outdated | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
n/a |
||
| Issue Links: |
|
||||||||
| 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 |
|
HierarchyManager exposes the following mutator methods:
In all cases where these methods are used, they are used: a) ONCE only, and It would better reflect the manner in which HierarchyManager is used if the fields 'startPage', 'workspace', and 'accessManager' were set only via the constructor, and the mutator methods removed. |
| Comments |
| Comment by Sameer Charles [ 16/Apr/07 ] |
|
DefaultHierarchyManager can be constructed together with 'startPage', 'workspace', and 'accessManager' but I would vote against to make it |