Package com.sri.emo.dbobj.model_tree

This package allows assembling of Emo nodes into a tree hierarchy where related nodes, attributes, parts, etc are loaded into this tree.

See:
Description

Interface Summary

Model	This represents the 'public' interface for traversing the model and reading it.
ModelNode	Represents a particular node on the model tree.
ModelVisitable	Interface that extends IViewable to include Visitor capabilities.
ModelVisitor	Visitor that allows for visiting of IViewable interface objects.
MutableModelNode	A node in the model tree that can have its children modified
TreeTraversalListener	Specific to the Iterator inherant with the model tree.

Class Summary

AbstractModelNode	Simple base class of all the mutable nodes.
DefaultModel	Default implementation of the 'model' interface.
DefaultModelFactory	Factory that builds a tree hierarchy from the Nodes.
DefaultModelNode	Default Model node used for nesting ModelVisitable data.
ModelDepthFirstIterator	Implementation of Iterator that allows depth first iteratation over all the nodes in a model.
ModelFillStatus	A pseudo enumeration type for defining status of the model tree in terms of filled out slots.
NodeCompletionStatus	Object represents a recursive/truncation/completion status inside the model.
NoParentNode	Special Case instance for no parents in a model.

Exception Summary

ViewVisitorException

Exception that is thrown whenever something happens while visiting a node.

Package com.sri.emo.dbobj.model_tree Description

This package allows assembling of Emo nodes into a tree hierarchy where related nodes, attributes, parts, etc are loaded into this tree. Once the assembly is complete, then you Visit the nodes to operate on the tree in a unified way. For example: to give the node hierarchy into a view that the TreeView tag can handle you:

1. Use DefaultModelFactory to construct a tree based on the node. Use maximumLevels to prevent infinite recursion that is possible while covering the tree.
2. Iterate the model using Model.iterator() function.
3. Visit each node with a TreeViewVisitor to build a unified tree view. (Visiting transforms the tree)
4. Deposite the results of the TreeViewVisitor onto the request context.