AddAttribute (XmlNode function): Difference between revisions
m (1 revision) |
m (tags and links) |
||
Line 2: | Line 2: | ||
This callable function adds an Attribute node to the method Element node. | This callable function adds an Attribute node to the method Element node. | ||
==Syntax== | ==Syntax== | ||
{{Template:XmlNode:AddAttribute syntax}} | {{Template:XmlNode:AddAttribute syntax}} | ||
Line 7: | Line 8: | ||
<table class="syntaxTable"> | <table class="syntaxTable"> | ||
<tr><th><i>%nod</i></th> | <tr><th><i>%nod</i></th> | ||
<td>If specified, an <var>XmlNode</var> that is set to point to the Attribute node that is added. </td></tr> | <td>If specified, an <var>XmlNode</var> that is set to point to the <var class="term">Attribute</var> node that is added. </td></tr> | ||
<tr><th><i>nod</i></th> | <tr><th><i>nod</i></th> | ||
<td><var>XmlNode</var> that points to the Element node parent of the added Attribute. </td></tr> | <td><var>XmlNode</var> that points to the <var>Element</var> node parent of the added <var class="term">Attribute</var>. </td></tr> | ||
<tr><th><i>name</i></th> | <tr><th><i>name</i></th> | ||
<td>A <var>Unicode</var> string that is the name of the added Attribute. | <td>A <var>Unicode</var> string that is the name of the added <var class="term">Attribute</var>. | ||
<p class=" | <p>Multiple <var class="term">Attributes</var> with the same name may <b><i>not</i></b> be added to a single parent <var>Element</var> (in contrast with the <var>[[AddElement_(XmlDoc/XmlNode_function)|Add Element]]</var> method, which allows multiple <var>Elements</var> with the same name to be added to a single parent <var>Element</var>). 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]]).</p></td></tr> | ||
</ | |||
<tr><th><i>value</i></th> | <tr><th><i>value</i></th> | ||
<td>A <var>Unicode</var> 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. </td></tr> | <td>A <var>Unicode</var> string that is the value of the added <var class="term">Attribute</var>; stored exactly as is, that is, without whitespace normalization nor conversion of any substring which may be equal to a character or entity reference. </td></tr> | ||
<tr><th><i>URI</i></th> | <tr><th><i>URI</i></th> | ||
<td>A <var>Unicode</var> 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).</td></tr> | <td>A <var>Unicode</var> string that is the Uniform Resource Identifier of the namespace of the name of the added <var class="term">Attribute</var>. This is an optional argument (see "Usage Notes," below).</td></tr> | ||
</table> | </table> | ||
==Usage notes== | ==Usage notes== | ||
<ul> | <ul> | ||
<li>Since the return value of <var>AddAttribute</var> is frequently not needed, | <li>Since the return value of <var>AddAttribute</var> is frequently not needed, you may want to Call it instead of saving its return value. | ||
you may want to Call it instead of saving its return value. | <li><var class="term">Attribute</var> nodes are kept in the order in which they are added. | ||
<li>Attribute nodes are kept in the order in which they | <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>. | ||
are added. | 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>As of | <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). | ||
include only non-null EBCDIC characters that translate to <var>Unicode</var>. | <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>, | ||
As of | 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). | ||
converted to <var>Unicode</var>. | <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. | ||
For more information about the effects of this | <li>Processing of an <var>XmlDoc</var> is likely to be more efficient if you add nodes in document order (that is, top-to-bottom, left-to-right). | ||
change, see [[Strings and Unicode]]. | |||
<li>If the <i>URI</i> argument is present, it must not be the null string, | |||
< | |||
contain a prefix, and the <var>XmlDoc</var> | |||
If there is no such declaration in effect at the | |||
Element pointed to by < | |||
is added at that Element, unless it would conflict with an existing declaration | |||
at the Element (which cancels the request). | |||
<li>If the <i>URI</i> argument is | |||
omitted, < | |||
contains a prefix, and the <var>XmlDoc</var> | |||
there must be a namespace declaration for the prefix in effect at the | |||
element pointed to by < | |||
<li>To modify the value stored in an Attribute node, | |||
change the Value property of an <var>XmlNode</var> that points to | |||
the Attribute node. | |||
<li>Processing of an <var>XmlDoc</var> is likely to be more efficient if | |||
you add nodes in document | |||
order (that is, top-to-bottom, left-to-right). | |||
</ul> | </ul> | ||
==Example== | |||
The following fragment adds the attribute named "option" to the element pointed to by <code>%nod</code>: | |||
<p class="code">%nod:AddAttribute('option', 'abc') | |||
</p> | |||
==Request-Cancellation Errors== | |||
<ul> | <ul> | ||
<li>< | <li><var class="term">Nod</var> is not an <var>Element</var> node. | ||
<li>< | <li><var class="term">Name</var> violates the rules for an XML attribute name. | ||
XML attribute name. | <li><var class="term">Name</var> is prefixed, but the <var>XmlDoc</var> Namespace property is None. | ||
<li>< | <li><var class="term">Name</var> is the name of an attribute already present in the node pointed to by <var class="term">nod</var>. | ||
is None. | <li><var class="term">Name</var> prefixed and Namespace On, but URI missing and no declaration for prefix in scope. | ||
<li>< | <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 — see [[InvalidChar (obsolete XmlDoc property)#Usage Notes|"Usage Notes for the InvalidChar property"]].</p> | ||
present in the node pointed to by < | <li><var class="term">URI</var> violates the rules for an | ||
<li>< | |||
declaration for prefix in scope. | |||
<li>< | |||
XML attribute value (that is, it contains an invalid character). | |||
Note that as of | |||
method — see [[InvalidChar (obsolete XmlDoc property)#Usage Notes|Usage Notes for the InvalidChar property]]. | |||
<li>< | |||
absolute Uniform Resource Identifier. | absolute Uniform Resource Identifier. | ||
<li>< | <li><var class="term">URI</var> specified and Namespace property is not <code>On</code> or <var class="term">name</var> is not prefixed. | ||
< | <li><var class="term">URI</var> specified and prefix of <var class="term">name</var> is declared with a different URI at the <var>Element</var> pointed to by <var class="term">nod</var> (not simply in scope at that <var>Element</var>). | ||
<li>< | |||
is declared with a different URI at the Element pointed to by < | |||
(not simply in scope at that Element). | |||
<li>Insufficient free space exists in CCATEMP. | <li>Insufficient free space exists in CCATEMP. | ||
</ul> | </ul> | ||
==See also== | ==See also== | ||
{{Template:XmlNode:AddAttribute footer}} | {{Template:XmlNode:AddAttribute footer}} |
Revision as of 07:07, 4 February 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
%nod | 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 — 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.