[MAGNOLIA-2362] core: improve content navigation via API Created: 12/Sep/08  Updated: 23/Jan/13  Resolved: 18/Sep/08

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

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Teresa Miyar
Resolution: Fixed Votes: 0
Labels: mme_sprint1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2363 core: multivalue support Closed
is related to MAGNOLIA-2421 Utility class to navigate in siblings Closed
is related to MAGNOLIA-2422 Extract ContentUtil.Visitor and Conte... Closed
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   

The magnolia API does not expose all node navigation features which are defined by JCR. In the past I had to fall back on the jcr node now and then. What I mainly miss are the following methods:

  • NodeData.getParent()
  • Content.getHierarchyManager()
  • HierarchyManager.getName()


 Comments   
Comment by Philipp Bracher [ 12/Sep/08 ]

While we add the support for multi values we might add this methods too.

Comment by Philipp Bracher [ 03/Oct/08 ]

I removed the throws RepositoryException on getHierarchyManager()

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