Differences between revisions 1 and 2
Revision 1 as of 2006-04-03 19:37:04
Size: 1051
Editor: JukkaZitting
Comment:
Revision 2 as of 2009-09-20 23:45:11
Size: 1051
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
Together with ["nt:folder"] and other subtypes this node type implements the Composite design pattern for storing structured node hierarchies. Node hierarchies based on ["nt:hierarchyNode"] subtypes differ from hierarchies based on ["nt:unstructured"] in that each ["nt:hierarchyNode"] node has a distinct character (e.g. branch or leaf node) and semantics whereas ["nt:unstructured"] nodes have no specified interpretation Together with [[nt:folder]] and other subtypes this node type implements the Composite design pattern for storing structured node hierarchies. Node hierarchies based on [[nt:hierarchyNode]] subtypes differ from hierarchies based on [[nt:unstructured]] in that each [[nt:hierarchyNode]] node has a distinct character (e.g. branch or leaf node) and semantics whereas [[nt:unstructured]] nodes have no specified interpretation
Line 18: Line 18:
 * ["nt:folder"] has ["nt:hierarchyNode"]s as child nodes
 * ["nt:hierarchyNode"] is the base type of ["nt:file"], ["nt:linkedFile"], and ["nt:folder"]
 * [[nt:folder]] has [[nt:hierarchyNode]]s as child nodes
 * [[nt:hierarchyNode]] is the base type of [[nt:file]], [[nt:linkedFile]], and [[nt:folder]]

Abstract base type for nodes in a structured node hierarchy.

Definition

[nt:hierarchyNode]
- jcr:created (DATE) autocreated protected INITIALIZE

Description

Together with nt:folder and other subtypes this node type implements the Composite design pattern for storing structured node hierarchies. Node hierarchies based on nt:hierarchyNode subtypes differ from hierarchies based on nt:unstructured in that each nt:hierarchyNode node has a distinct character (e.g. branch or leaf node) and semantics whereas nt:unstructured nodes have no specified interpretation

This node type is normally only used as a base for other node types, as there is usually little point in creating a node whose only content is the creation date and other metadata specified by possible mixin types.

Comments and questions

nt:hierarchyNode (last edited 2009-09-20 23:45:11 by localhost)