Hi srikanth,
Singleton child nodes however are associated with their parent node on a per node basis.
Irrespective of the number of elements in the parent node's element collection, there will only ever be one instance of the singleton child node .
The Singleton child node holds the data relevant for the element at the lead selection in the parent node's element collection.
Singleton child nodes must be created by their parent node. Since there can only ever one instance of singleton child node. It is impossible for an element in a parent node collection to create singleton child node.
Since the context root node always has exactly one element, all the nodes that have the context root node as their immediate parent must, by definition be singleton nodes.
Further to this, the definition of a Singleton child node immediately implies that it must be repopulated every time the lead selection in its parent node changes. This job is performed by declaring a Supply Function for the singleton child node. Selection Cardinality:
All the context nodes maintain a collection of elements, where an element is a single instance of all the node's child entities. During the operation of a Webdynpro controller, it is often becomes necessary to make certain node elements as requiring processing
Check this for more details
<a href="http://help.sap.com/saphelp_nw04/helpdata/en/81/95384162316532e10000000a1550b0/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/81/95384162316532e10000000a1550b0/frameset.htm</a>
regards
Sumit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.