Community articleUFLSetAttribute function
Added by IBM contributorIBM on August 16, 2011
Rate this article 1 starsRate this article 2 starsRate this article 3 starsRate this article 4 starsRate this article 5 stars

No abstract provided.


This function sets the value of a specific attribute for a node. For example, the following XFDL represents a value node:
   <value custom:myAtt="x"></value>

To change the custom attribute, you would use setAttribute. If the attribute does not already exist, setAttribute will create it and assign the appropriate value.
Note: Do not use UFLSetAttribute to set the compute attribute. Instead, use


   r_error UFLSetAttribute(
      formNodeP theFormNode,
      r_charP theNamespaceURI,
      r_charP theAttribute,
      r_charP theValue


Table 1. Function parameters
theFormNode formNodePThe node to set the attribute for.
theNamespaceURIr_charPThe namespace URI for the attribute. For example:

theAttributer_charPThe local name of the attribute. For example, encoding.
theValuer_charPThe value to assign to the attribute.


OK on success or an error code on failure.


Attributes and the null namespace:
If an attribute is on a node in a non-XFDL namespace, and that attribute has no namespace prefix, then the attribute is in the null namespace. For example, the following node is the custom namespace, as is the first attribute, but since the second attribute does not have a namespace prefix, it is in the null namespace:
   <custom:processing custom:stage="2" user="tjones">

When an attribute is the null namespace, you may either provide a NULL value for the namespace URI or use the namespace URI for the containing element.
For example, to indicate user attribute on the processing node, you could use the null namespace or the custom namespace URI.
Attributes and namespace prefixes:
If you refer to an attribute with a namespace prefix, UFLSetAttribute first looks for a complete match, including both prefix and attribute name. If it does not find a match, it will look for a matching attribute name that has no prefix but whose containing element has the same namespace.
For example, assume that the custom namespace and the test namespace both resolve to the same URI. In the following case, looking for the id attribute would locate the second attribute (test:id), since it has an explicit namespace declaration:
   <a xmlns:custom="ABC" xmlns:test="ABC">
      <custom:myElement id="1" test:id="2">

However, in the next case, the id attribute does not have an explicit namespace declaration. Instead, it inherits the custom namespace. However, since the inherited namespace resolves to the same URI, the id attribute is still located:
   <custom:myElement id="1">


The following example shows a shortcut method that sets a custom data attribute for a specific node. A node and a string containing the contents of the attribute are passed to the function, which then uses UFLSetAttribute to set the attribute for the node.
   r_error setCustomAttribute(formNodeP theNode, r_charP theContents)
      if (UFLSetAttribute(theNode, 
         "Data", theContents) != OK)
         fprintf(stderr, "Could not set attribute.");

Parent topic:
FormNodeP functions