[OAK-161] Refactor Tree#getChildStatus

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.4
• Component/s: core
• Assignee: Michael Dürig
• Reporter: Angela Schreiber
• Created: 29/Jun/12 13:42
• Updated: 14/Aug/12 09:28
• Resolved: 04/Jul/12 15:43

Description

as discussed today Tree#getChildStatus is a bit problematic from my point
of view as it requires the parent Tree to be always accessible. as discussed
and stated multiple times in the past that may not be always the case.

a part from the drawback it offers once we have access control in place
it doesn't work for the root node, which doesn't have a parent by definition.

therefore i would suggest to refactor the method to Tree#getStatus and make it
an implementation detail if the status is stored with the parent or the tree
itself.

Issue Links

• is related to: OAK-164 Replace Tree.remove(String) with Tree.remove()
• is related to: OAK-165 NodeDelegate should not use Tree.getChild() but rather Root.getTree()
• is related to: OAK-166 Add Tree.isRoot() method instead of relying on Tree.getParent() == null
• relates to: OAK-164 Replace Tree.remove(String) with Tree.remove()
• relates to: OAK-165 NodeDelegate should not use Tree.getChild() but rather Root.getTree()
• relates to: OAK-160 Make oak interfaces permission aware