Tutorial Addendum on Web Account and SOAP - SOAP Encoding

Multiple References and Annular References

    

To advice serializing assorted reference, SOAP encoding blueprint offers the afterward rule:

    

6. If serializing an labeled entering edge, "enc:id" aspect can be added to accommodate an identification

    

to the node. If this bulge has additional labeled entering edges, they can be after with "enc:ref" attributes

    

to accredit to the bulge by the identification authentic in the "enc:id" attribute. Of course, the amount of "enc:id"

    

must be unique.

    

Example 5 - Multi references: The afterward blueprint represents two admixture ethics administration the aforementioned sub value.

    

 

    
   --- Bill -->( )--- mother --->               

    
                                ( )<-- Mary ---

    
   --- Mike -->( )--- sister --->               

    

Using the "enc:id" and "enc:ref" attributes, this blueprint can be calmly after as:

    

 

    
   <Mary enc:id="101"/>

    
   <Bill>

    
    <mother enc:ref="#101"/>

    
   </Bill> 

    
   <Mike>

    
    <sister enc:ref="#101"/>

    
   </Mike> 

    

Example 6 - Annular References: The afterward blueprint represents two admixture ethics has anniversary additional as their sub values.

    

 

    
                 <--- son ------

    
   --- Bill -->( )             ( )<-- Mary ---

    
                 --- mother --->               

    

Using the "enc:id" and "enc:ref" attributes, this blueprint can aswell be calmly after as:

    

 

    
   <Mary enc:id="101">

    
    <son enc:ref="#102"/>

    
   </Mary> 

    
   <Bill enc:id="102">

    
    <mother enc:ref="#101"/>

    
   </Bill> 

    

Node Types

    

To advice anecdotic the blazon of node, SOAP encoding blueprint aswell offers the afterward rule:

    

7. If serializing an labeled entering edge, "enc:nodeType" aspect can be added to indicate

    

what affectionate of a amount this bulge represents. "enc:nodeType" may be one of the strings "simple"

    

or "struct" or "array".

    

Example:

    

 

    
   <currentCustomer enc:nodeType="struct">

    
    <id enc:nodeType="simple">2321</id>

    
    <name enc:nodeType="simple"></name>

    
    <isSmoking enc:nodeType="simple">false</isSmoking>

    
   </currentCustomer>

    

SOAP encoding Attributes and Namespace

    

As we can see from the antecedent sections, SOAP encoding blueprint defines the afterward attributes in its own

    

namespace, "http://www.w3.org/2003/05/soap-encoding".

    

 

    
   <... xmlns:enc="http://schemas.xmlsoap.org/soap/encoding" ...>

    
    <... enc:nodeType="simple" enc:id="...">

    
    </...>

    
    <... enc:nodeType="simple" enc:ref="..."/>

    
    <... enc:nodeType="array" enc:arraySize="..." enc:itemType="...">

    
     ...

    
    </..>

    
    <... enc:noteType="struct">

    
     ...

    
    </..>

    
   </...> 

    

Using SOAP encoding in SOAP Messages

    

SOAP encoding can be acclimated in SOAP attack blocks and SOAP bodies by allegorical the SOAP "encodingStyle" attribute

    

as encodingStyle="http://schemas.xmlsoap.org/soap/encoding/". Actuality is a SOAP bulletin archetype with SOAP encoding:

    

 

    
<?xml version="1.0"?>

    
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">

    
 <env:Header 

    
    env:encodingStyle="http://www.w3.org/2003/05/soap-encoding"

    
    xmlns:enc="http://www.w3.org/2003/05/soap-encoding">

    
  <h:expense xmlns:h="http://www.yang.com"

    
     env:role="http://www.w3.org/2003/05/soap-envelope/role/next"

    
     env:mustUnderstand="true">

    
  </h:expense>

    
 </env:Header>

    
 <env:Body 

    
    env:encodingStyle="http://www.w3.org/2003/05/soap-encoding"

    
    xmlns:enc="http://www.w3.org/2003/05/soap-encoding">

    
  <b:travel enc:nodeType="struct" xmlns:b="http://www.yang.com">

    
   <b:currency enc:id="euro">

    
    <b:rate>0.72</b:rate>

    
   </b:currency>

    
   <b:flight>429.00</b:flight>

    
  </b:travel>

    
  <b:shopping enc:nodeType="struct" xmlns:b="http://www.yang.com">

    
   <b:currency enc:ref="#euro"/>

    
   <b:paris enc:nodeType="array" enc:arraySize="3" enc:itemType="xsi:float">

    
     <b:item>29.00</b:item>

    
     <b:item>99.00</b:item>

    
     <b:item>19.00</b:item>

    
   </b:paris>

    
  </b:shopping>

    
 </env:Body>

    
</env:Envelope>

    

Conclusions

    

SOAP encoding is based on SOAP date model.

    

SOAP encoding basal rules are simple to remember: entering bend makes an XML element, and outbound edges create sub elements.

    

Question, can a accumulation of nodes be after into two altered XML messages?