`number', `element' or `referid' specify the node. If none of them is given then the node
refers to a parent NodeProvider, and simply mirrors it, which can e.g. be useful to assign
it a (new) id. The 'parent' node-provider can also be determined by use of the '_node'
variable. This last behaviour can be enforced using node="" as attribute (which can be useful
e.g. in tag-file fragments).
The node number or alias identifying this node in MMBase.
What to do if the node is not found. The default is to throw an exception.
|skip|skipbody||Simply skip the body if the node is not found
|message||Just say in the page that the node was not found
|throw|throwexception||Throw an exception if the node is not found
Will not throw an exception, but will evaluate the body,
simply providing `null' as node. This will probably lead to
other (less clear) exceptions. But if you prefer it that
way, it is possible. Use on own risk!
Like 'skip' but also logs a message.
element (Either `number', `element' or `referid' must be supplied.)
The name of a node field of the current node. This can for instance be the `rnumber' field
of a relation, the `destination' field of an oalias, etc. A common use is to specify the
name of the node manager to identify a node in a list or related list tag (clusternode
providers). In this case, the nodemanager name behaves like a special virtual node field of
the surrounding cluster node, indicating the individual nodes that make up the cluster node.