AddXml (HttpRequest subroutine): Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 65: Line 65:
does it cause resumption of readability line-ends or indents if they were
does it cause resumption of readability line-ends or indents if they were
suspended by a containing <code>xml:space="preserve"</code>.
suspended by a containing <code>xml:space="preserve"</code>.
</ul>


<div id="sortcan"></div>
<div id="sortcan"></div>
<li>The following example shows the effect of the <var>SortCanonical</var> option:<p class="code"> Begin   
==Examples==
The following example shows the effect of the <var>NoEmptyElt</var> option:<p class="code">Begin   
%d is object Xmldoc   
%d is object Xmldoc   
%d = new   
%d = new   
Line 76: Line 78:
Text To %sl   
Text To %sl   
<top p:abc="p" q:xyz="q"     
<top p:abc="p" q:xyz="q"     
   xmlns:p="urn:p" xmlns:q="http://q.com"
   xmlns:p="urn:p" xmlns:q=<nowiki>"http://q.com"</nowiki>
  xmlns="urn:default"   
   name="t" id="z15"   
   name="t" id="z15"   
/>   
/>   
End Text   
End Text   
%d:LoadXml(%sl)   
%d:LoadXml(%sl)   
%htr:AddXml(%d, 'SortCanonical NoEmptyElt')   
%htr:AddXml(%d, 'NoEmptyElt')   
Print %d:Serial(, 'EBCDIC SortCanonical NoEmptyElt')   
Print %d:Serial(, 'EBCDIC NoEmptyElt')   
End </p>  
End </p>  


The <var>Print</var> statement above (which uses the <var>[[Serial (XmlDoc/XmlNode function)|Serial]]</var> method of the <var class="product>[[Janus SOAP]]</var> [[XmlDoc API]]) displays the resulting <var>XmlDoc</var> content added to the <var>HttpRequest</var> object (formatted with some newlines for the sake of instruction): <p class="code"><top
The <var>Print</var> statement above (which uses the <var>[[Serial (XmlDoc/XmlNode function)|Serial]]</var> method of the <var class="product">[[Janus SOAP]]</var> [[XmlDoc API]]) displays the resulting <var>XmlDoc</var> content added to the <var>HttpRequest</var> object (formatted with some newlines for the sake of instruction): <p class="code"><top
  xmlns="urn:default"   
   xmlns:p="urn:p" xmlns:q=<nowiki>"http://q.com"</nowiki>      
   xmlns:p="urn:p" xmlns:q="http://q.com"     
   p:abc="p" q:xyz="q"
   id="z15" name="t"    
   name="t" id="z15">   
   q:xyz="q" p:abc="p" >   
</top> </p>
</top> </p>


Comments:
<var>NoEmptyElt</var> produces an STag (<code><top ...></code>) and an ETag (<code></top></code>) for an empty element, rather than just the EmptyElemTag (<code><top ...></code>).
<ul>
<li>The reason for the name (<var>SortCanonical</var>) is that this ordering is part of the specification of the <i><b>Canonical XML Recommendation</b></i> (http://www.w3.org/TR/xml-c14n) and the <i><b>Exclusive Canonical XML Recommendation</b></i> (http://www.w3.org/TR/xml-exc-c14n), which constrain serializations to facilitate processing such as digital signatures.
<li>Notice the use of the <var>NoEmptyElt</var> option above. This produces an STag (<code><top ...></code>) and an ETag (<code></top></code>) for an empty element, rather than just the EmptyElemTag (<code><top ...></code>).
The canonical XML recommendations state that an STag/ETag pair, rather than an EmptyElemTag, is the serialization for an empty element.
<li>Although <var>SortCanonical</var> uses the Unicode sort sequence, this is limited to Unicode values less than 256 (as of version 6.9 of <var class="product">Janus SOAP</var>, so it is accomplished with an 8-byte EBCDIC to 8-byte Unicode table, which is (for all intents and purposes) merely an EBCDIC-to-ASCII translation. </ul>
</ul>




==See also==
==See also==
{{Template:HttpRequest:AddXml footer}}
{{Template:HttpRequest:AddXml footer}}

Revision as of 00:05, 17 June 2011

Add an XmlDoc to POST data for this request (HttpRequest class)


This subroutine adds a Janus SOAP XmlDoc object instance to the HTTP Post data that is subsequently sent on a Post method invocation.

Syntax

httpRequest:AddXml( doc, [options])

Syntax terms

%httpreq A previously defined and instantiated HttpRequest object.
doc An XmlDoc object that contains an instantiated XmlDoc object.
xmloptions Any combination of the following options (but single occurrences only):
  • AllowXmlDecl or NoXmlDecl
    AllowXmlDecl, the default, produces the "XML Declaration" (that is, <?xml version=...?>) if the value of the Version property in doc is a non-null string. NoXmlDecl omits the XML declaration.
  • Indent n
    Inserts space characters and line-ends into the serialized string such that if the string is broken at the line-ends and displayed as a tree, the display of each lower level in the subtree is indented n spaces from the previous level's starting point. You may also specify CR, LF, CRLF, or Newline (see below). If Indent is specified and no line-end options are also specified, Newline is implied.
  • CR (carriage-return), LF (linefeed), CRLF (carriage-return followed by a linefeed), or Newline (line-end set for the Janus Web connection)
    Inserts one of these line-end options to provide line breaks in the serialized output.
  • NoEmptyElt
    Deprecated as of Sirius Mods Version 7.0, this option ensures that all empty elements are serialized with a start tag followed by an end tag. The default is to serialize an empty element with an empty element tag (as in <middleName/>).
  • OmitNullElement
    An Element node that has no children and no Attributes will not be serialized, unless it is the top level Element in the subtree being serialized.
  • SortCanonical
    This deprecated option, serializes namespace declarations and attributes in sorted order (from lowest to highest with Unicode code ordering). It is superseded by the Serial method ExclCanonical option.
Note: These options are described in greater detail in "XmlDoc API serialization options"

Usage notes

  • The XmlDoc that is passed is serialized into the post data of the request being built. It is not required that you serialize the XmlDoc first.
  • Invoking this method erases any post data previously added by AddXml or AddLongString method calls.
  • If you do not explicitly set a content-type HTTP request header via AddHeader, AddXml generates a content-type header of "text/xml" upon a Post. To suppress this automatic header generation, you can set the AutoSendXmlContentType property to False.
  • The xmloptions may be specified in any case, for example, you can use either NoXmlDecl or noxmldecl, interchangeably.
  • If one of the line-end (CR, LF, CRLF) options or if Indent is specified, and an element to be serialized has the xml:space="preserve" attribute, then within the serialization of that element and its descendants, no line-end (nor indentation) characters are inserted to provide readability. In addition, the xml:space="default" attribute has no effect under these options: specified by itself, it does not influence serialization, nor does it cause resumption of readability line-ends or indents if they were suspended by a containing xml:space="preserve".

Examples

The following example shows the effect of the NoEmptyElt option:

Begin %d is object Xmldoc %d = new %htr is object HttpRequest %htr = new %sl is object Stringlist %sl = new Text To %sl <top p:abc="p" q:xyz="q" xmlns:p="urn:p" xmlns:q="http://q.com" name="t" id="z15" /> End Text %d:LoadXml(%sl) %htr:AddXml(%d, 'NoEmptyElt') Print %d:Serial(, 'EBCDIC NoEmptyElt') End

The Print statement above (which uses the Serial method of the Janus SOAP XmlDoc API) displays the resulting XmlDoc content added to the HttpRequest object (formatted with some newlines for the sake of instruction):

<top xmlns:p="urn:p" xmlns:q="http://q.com" p:abc="p" q:xyz="q" name="t" id="z15"> </top>

NoEmptyElt produces an STag (<top ...>) and an ETag (</top>) for an empty element, rather than just the EmptyElemTag (<top ...>).


See also