AddAttribute (XmlNode function): Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (1 revision)
m (1 revision)
Line 24: Line 24:
<li><var class="term">Attribute</var> nodes are kept in the order in which they are added.
<li><var class="term">Attribute</var> nodes are kept in the order in which they are added.
<li>As of <var class="product">[[Sirius Mods|"Sirius Mods"]]</var> Version 7.3, the <var>AddAttribute</var> method arguments may include only non-null EBCDIC characters that translate to <var>Unicode</var>.
<li>As of <var class="product">[[Sirius Mods|"Sirius Mods"]]</var> Version 7.3, the <var>AddAttribute</var> method arguments may include only non-null EBCDIC characters that translate to <var>Unicode</var>.
As of <var class="product">[[Sirius Mods|"Sirius Mods"]]</var> Version 7.6, these argument strings are <var>Unicode</var> or are converted to <var>Unicode</var>.  For more information about the effects of this Version 7.6 change, see <var>[[XmlNodelist_class#Strings_and_Unicode_with_the_XmlDoc_API|"Strings and Unicode"]]</var>.
As of <var class="product">[[Sirius Mods|"Sirius Mods"]]</var> Version 7.6, these argument strings are <var>Unicode</var> or are converted to <var>Unicode</var>.  For more information about the effects of this Version 7.6 change, see <var>[[XmlNodelist_class#Strings_and_Unicode_with_the_XmlDoc_API|Strings and Unicode]]</var>.
<li>If the <i>URI</i> argument is present, it must not be the null string, <var class="term">name</var> must contain a prefix, and the <var>XmlDoc's</var> <var>[[Namespace_(XmlDoc_property)|"Namespace property"]]</var> must be <code>On</code>.  If there is no such declaration in effect at the <var>Element</var> pointed to by <var class="term">nod</var> for that prefix, a declaration is added at that <var>Element</var>, unless it would conflict with an existing declaration at the <var>Element</var> (which cancels the request).
<li>If the <i>URI</i> argument is present, it must not be the null string, <var class="term">name</var> must contain a prefix, and the <var>XmlDoc's</var> <var>[[Namespace_(XmlDoc_property)|Namespace property]]</var> must be <code>On</code>.  If there is no such declaration in effect at the <var>Element</var> pointed to by <var class="term">nod</var> for that prefix, a declaration is added at that <var>Element</var>, unless it would conflict with an existing declaration at the <var>Element</var> (which cancels the request).
<li>If the <i>URI</i> argument is omitted, <var class="term">name</var> contains a prefix, and the <var>XmlDoc's</var> <var>[[Namespace_(XmlDoc_property)|"Namespace property"]]</var> is <code>On</code>,
<li>If the <i>URI</i> argument is omitted, <var class="term">name</var> contains a prefix, and the <var>XmlDoc's</var> <var>[[Namespace_(XmlDoc_property)|Namespace property]]</var> is <code>On</code>,
there must be a namespace declaration for the prefix in effect at the element pointed to by <var class="term">nod</var> (otherwise the request is canceled).
there must be a namespace declaration for the prefix in effect at the element pointed to by <var class="term">nod</var> (otherwise the request is canceled).
<li>To modify the value stored in an <var class="term">Attribute</var> node, change the Value property of an <var>XmlNode</var> that points to the <var class="term">Attribute</var> node.
<li>To modify the value stored in an <var class="term">Attribute</var> node, change the Value property of an <var>XmlNode</var> that points to the <var class="term">Attribute</var> node.
Line 45: Line 45:
<li><var class="term">Name</var> prefixed and Namespace On, but URI missing and no declaration for prefix in scope.
<li><var class="term">Name</var> prefixed and Namespace On, but URI missing and no declaration for prefix in scope.
<li><var class="term">Value</var> violates the rules for an XML attribute value (that is, it contains an invalid character).
<li><var class="term">Value</var> violates the rules for an XML attribute value (that is, it contains an invalid character).
<p><b>Note:</b> that as of <var>Sirius Mods</var> Version 7.6, this check can no longer be bypassed using the InvalidChar method &amp;mdash; see [[InvalidChar (XmlDoc property)#Usage notes|"Usage notes for the InvalidChar property"]].</p>
<p><b>Note:</b> that as of <var>Sirius Mods</var> Version 7.6, this check can no longer be bypassed using the InvalidChar method &amp;amp;mdash; see [[InvalidChar (XmlDoc property)#Usage notes|"Usage notes for the InvalidChar property"]].</p>
<li><var class="term">URI</var> violates the rules for an
<li><var class="term">URI</var> violates the rules for an
absolute Uniform Resource Identifier.
absolute Uniform Resource Identifier.

Revision as of 17:20, 4 May 2011

Add Attribute to Element node (XmlNode class)

[Requires Janus SOAP]

This callable function adds an Attribute node to the method Element node.

Syntax

[%outNod =] nod:AddAttribute( name, value, [uri])

Syntax terms

%outNod If specified, an XmlNode that is set to point to the Attribute node that is added.
nod XmlNode that points to the Element node parent of the added Attribute.
name A Unicode string that is the name of the added Attribute.

Multiple Attributes with the same name may not be added to a single parent Element (in contrast with the Add Element method, which allows multiple Elements with the same name to be added to a single parent Element). The name must conform to the XML syntax rules for an attribute name; the maximum length of each of the prefix part and local name part is 127 characters (100 characters prior to version 7.7 of Janus SOAP).

value A Unicode string that is the value of the added Attribute; stored exactly as is, that is, without whitespace normalization nor conversion of any substring which may be equal to a character or entity reference.
uri A Unicode string that is the Uniform Resource Identifier of the namespace of the name of the added Attribute. This is an optional argument (see "Usage Notes", below).

Usage notes

  • Since the return value of AddAttribute is frequently not needed, you may want to Call it instead of saving its return value.
  • Attribute nodes are kept in the order in which they are added.
  • As of "Sirius Mods" Version 7.3, the AddAttribute method arguments may include only non-null EBCDIC characters that translate to Unicode. As of "Sirius Mods" Version 7.6, these argument strings are Unicode or are converted to Unicode. For more information about the effects of this Version 7.6 change, see Strings and Unicode.
  • If the URI argument is present, it must not be the null string, name must contain a prefix, and the XmlDoc's Namespace property must be On. If there is no such declaration in effect at the Element pointed to by nod for that prefix, a declaration is added at that Element, unless it would conflict with an existing declaration at the Element (which cancels the request).
  • If the URI argument is omitted, name contains a prefix, and the XmlDoc's Namespace property is On, there must be a namespace declaration for the prefix in effect at the element pointed to by nod (otherwise the request is canceled).
  • To modify the value stored in an Attribute node, change the Value property of an XmlNode that points to the Attribute node.
  • Processing of an XmlDoc is likely to be more efficient if you add nodes in document order (that is, top-to-bottom, left-to-right).

Example

The following fragment adds the attribute named "option" to the element pointed to by %nod:

%nod:AddAttribute('option', 'abc')

Request-Cancellation Errors

  • Nod is not an Element node.
  • Name violates the rules for an XML attribute name.
  • Name is prefixed, but the XmlDoc Namespace property is None.
  • Name is the name of an attribute already present in the node pointed to by nod.
  • Name prefixed and Namespace On, but URI missing and no declaration for prefix in scope.
  • Value violates the rules for an XML attribute value (that is, it contains an invalid character).

    Note: that as of Sirius Mods Version 7.6, this check can no longer be bypassed using the InvalidChar method &amp;mdash; see "Usage notes for the InvalidChar property".

  • URI violates the rules for an absolute Uniform Resource Identifier.
  • URI specified and Namespace property is not On or name is not prefixed.
  • URI specified and prefix of name is declared with a different URI at the Element pointed to by nod (not simply in scope at that Element).
  • Insufficient free space exists in CCATEMP.

See also