Asithasbeenmentionedabovethe_rich_tree_componentallowsren

1、As it has been mentioned above the component allows rendering any tree-like data model. The component interacts with data model through TreeNode interface (org.richfaces.model.TreeNode ( HYPERLINK /file-access/default/members/jbossrichfaces/freezone/docs/apidoc_framework/org/richfaces/model/TreeNode

2、.html /file-access/default/members/jbossrichfaces/freezone/docs/apidoc_framework/org/richfaces/model/TreeNode.html) that is used for tree nodes representation. The value attribute of the component contains a nodes structure defined in a bean property. The property keeps a structure of objects that i

3、mplement TreeNode interface. TreeNode has a property data (see org.richfaces.model.TreeNode ( HYPERLINK /file-access/default/members/jbossrichfaces/freezone/docs/apidoc_framework/org/richfaces/model/TreeNode.html /file-access/default/members/jbossrichfaces/freezone/docs/apidoc_framework/org/richface

4、s/model/TreeNode.html). Data contained in the property are placed in a request scope variable, which name is defined with var attribute for the component.You can develop and use your own implementation for TreeNode interface or use a default implementation, which is defined with a default class Tree

5、NodeImpl (org.richfaces.model.TreeNodeImpl ( HYPERLINK /file-access/default/members/jbossrichfaces/freezone/docs/apidoc_framework/org/richfaces/model/TreeNodeImpl.html /file-access/default/members/jbossrichfaces/freezone/docs/apidoc_framework/org/richfaces/model/TreeNodeImpl.html). There is XmlTreeD

6、ataBuilder class (ponent.xml.XmlTreeDataBuilder ( HYPERLINK /file-access/default/members/jbossrichfaces/freezone/docs/apidoc/org/richfaces/component/xml/XmlTreeDataBuilder.html /file-access/default/members/jbossrichfaces/freezone/docs/apidoc/org/richfaces/component/xml/XmlTreeDataBuilder.html) that

7、allows transforming XML into structures of objects containing XmlNodeData (ponent.xml.XmlNodeData ( HYPERLINK /file-access/default/members/jbossrichfaces/freezone/docs/apidoc_framework/org/richfaces/component/xml/XmlNodeData.html /file-access/default/members/jbossrichfaces/freezone/docs/apidoc_frame

8、work/org/richfaces/component/xml/XmlNodeData.html) instances as data, which could be represented by the component.Its possible to define a visual representation of a data model node (to define a node icon) and its behavior in a compliance with data contained in this node (with a value of the var att

9、ribute). The node behavior is defined by components nested to the (it could be links or buttons, for example). For these purposes you should use nodeFace attribute. For each tree node a value of nodeFace attribute is evaluated and with a value of type attribute equal to a value of nodeFace is used f

10、or node representation.An example is placed below: Example: . .This is a result:In the example when each node of data model is processed, data contained in the property data of TreeNode interface are placed in a request scope variable, which name is defined with var attribute. The value of the nodeF

11、ace attribute is evaluated in compliance with data placed in the var attribute. And for the node representation is used corresponding component (with a value of type attribute equal to a value of nodeFace). For example, during processing of data model an object with name Chris Rea was placed in the

12、var attribute. Then value of nodeFace attribute is evaluated as artist. Thus, for node representation the with type equal to artist is used.There are some essential moments in a nodeFace attribute usage. For their description its necessary to define notions of a typeless node and a default node.The

13、typeless node is the first component (from all children nodes nested to the component) with not defined type attribute and defined rendered attribute. The typeless node is used for representation when nodeFace attribute is null.Default node has the following interior presentation:varAttributeName is

14、 a value for var attribute.Default node is used in the following cases:nodeFace attribute is defined, but its value isnt equal to any type attribute value from all children nodes;nodeFace attribute is defined and its value is equal to a value of some type attribute from all children nodes , but the

15、value of rendered attribute for this node is false.There is also one especial moment in the type and rendered attributes usage. Its possible to define several components with the equal values of type attribute and different values of rendered attribute. It provides the possibility to define differen

16、t representation for the same nodes type. In the example with artists and their albums (see above) its possible to represent artists that are available for sale and artists that are not available. An example is placed below:Example: . . .This is a result:In the example the components has equal values of the type attribute. In a compliance with value of the