[MAGNOLIA-2750] NodeData.getHierarchyManager() should not throw RepositoryException Created: 27/May/09  Updated: 23/Jan/13  Resolved: 27/May/09

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

Type: Improvement Priority: Major
Reporter: Magnolia International 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)

 Description   

I don't see any reason it would or should do so. Content.getHierarchyManager does not, so if only for consistency's sake, I'd be in favor of removing this throws clause.



 Comments   
Comment by Magnolia International [ 27/May/09 ]

done on trunk

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