com.neurosys.common.hierarchy

Class HierarchyHelper

java.lang.Object

com.neurosys.common.hierarchy.HierarchyHelper

public class HierarchyHelper
extends Object

Constructor Summary

Constructors

Constructor and Description
HierarchyHelper()

Method Summary

Modifier and Type	Method and Description
static List<List<String>>	getNewHierarchySequence(String nodeHierarchy, String parentHierarchy, int sequence, List<String> hierachyCodesTaken)
static IHierarchialReference	getParent(Long parentId, List hierarchy) Do a DFS on the List-Tree and find the matching parent. TODO: consider replace with method in DAO that will fetch this data directly? For Small trees this is fine, but for large data sets Tree traversal maybe more expensive than a database call.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

HierarchyHelper

public HierarchyHelper()

Method Detail

getNewHierarchySequence

public static List<List<String>> getNewHierarchySequence(String nodeHierarchy,
                                                         String parentHierarchy,
                                                         int sequence,
                                                         List<String> hierachyCodesTaken)

Parameters:

nodeHierarchy - as the Code of node causing all this shifting. If it is part of set being shifted then one has to give it extra consideration

parentHierarchy -

sequence - as int, What is the desired location under parentHierarchy for the current parentHierarchy element

hierachyCodesTaken, - What are the hierarchy codes already taken under parentHierarchy. This may include nodeHierarchy if it is already under same parent. (common use case)

Returns:

getParent

public static IHierarchialReference getParent(Long parentId,
                                              List hierarchy)

Do a DFS on the List-Tree and find the matching parent.

TODO: consider replace with method in DAO that will fetch this data directly? For Small trees this is fine, but for large data sets Tree traversal maybe more expensive than a database call.

Parameters:

parentId -

hierarchy -

Returns:

@nullable true if no matches found