Tutorial Addendum on Web Account and SOAP - SOAP Encoding

This affiliate describes:

    

    
• What is SOAP encoding?
  
      



    
• How to handle assorted references and annular references?
  
      



    
• How to specify bulge types?
  
      



    
• How to using SOAP encoding in SOAP messages
  
      



    

What Is SOAP Encoding?

    

SOAP encoding is an addendum of the SOAP framework blueprint that defines how a data amount should

    

be encoded in an XML format. SOAP Data Archetypal is authentic as an accessory

    

in SOAP 1.2 specification.

    

SOAP encoding offers the afterward rules to catechumen any data amount authentic in SOAP data archetypal into

    

XML format. Converting a data amount into XML architecture is alleged serialization or encoding.

    

1. A simple amount bulge with a labeled entering bend will be after into a individual XML element

    

with the bend s characterization as the aspect s name and bulge amount as the aspect s argument content.

    

2. If serializing a bulge into an XML element, an "xsi:type" aspect can be added to specify

    

the amount blazon of this note. For added advice on "xsi:type", see the additional sections in this book.

    

3. A admixture amount bulge with labeled outbound edges, a data structure, will be after

    

into a individual XML aspect with adolescent elements. One outbound bend will be after into one adolescent element

    

with aspect s name according to the bend s label. The adjustment of adolescent elements is not significant.

    

4. A admixture amount bulge with non-labeled outbound edges, a data array, will be after

    

into a individual XML aspect with adolescent elements. One outbound bend will be after into one adolescent element

    

with aspect s name according to any characterization as continued as it s the aforementioned for all adolescent elements.

    

The adjustment of adolescent elements signifies the position ethics of outbound edges.

    

5. If serializing an array, an "enc:itemType" aspect can be added to specify the amount blazon of

    

its sub nodes, and an "enc:arraySize" aspect can be added to specify the amount of ethics in the array.

    

Example 1 - Simple amount with no reference: The afterward blueprint represents a simple amount of 3.14:

    

 

    
   (3.14)

    

Since this bulge has no entering edge, I assumption we can serialize it as XML aspect with any name:

    

 

    
   <value>3.14</value>

    

Example 2 - Simple amount with a called reference: The afterward blueprint represents a simple amount of 3.14

    

with a advertence name of "pi":

    

 

    
   --- pi -->(3.14) 

    

This bulge has an entering labeled edge. The consistent XML aspect should be called as the entering bend label.

    

 

    
   <pi>3.14</pi>

    

Example 3 - Admixture amount with called sub data elements: The afterward blueprint represents a admixture amount with a advertence name of "currentCustomer".

    

This admixture amount has 3 simple-value sub data elements referenced as "id", "name" and "isSmoking" respectively.

    

In some programming language, this admixture amount is alleged a structure:

    

 

    
                         (2321)

    
                           ^

    
                           |

    
                          id

    
                           |

    
   --- currentCustomer -->( )-- name -->()

    
                           |

    
                       isSmoking

    
                           |

    
                           v

    
                        (false)

    

This bulge has an entering labeled edge. The consistent XML aspect should be called as the entering bend label:

    

 

    
   <currentCustomer>

    
    <id>2321</id>

    
    <name></name>

    
    <isSmoking>false</isSmoking>

    
   </currentCustomer>

    

Example 4 - Admixture amount with positioned sub data elements: The afterward blueprint represents a admixture amount with a advertence name of "colors".

    

This admixture amount has 3 simple-value sub data elements referenced with no names, but with positions.

    

In some programming languages, this admixture amount is alleged an array:

    

 

    
                (Red)

    
                  ^

    
                  |

    
                  0

    
                  |

    
   --- colors -->( )----1--->(Green)

    
                  |

    
                  2

    
                  |

    
                  v

    
                (Blue)

    

Obviously, this bulge represents an array:

    

 

    
   <colors enc:arraySize="3" enc:itemType="xsd:string">

    
    <item>Red</item>

    
    <item>Green</item>

    
    <item>Blue</item>

    
   </colors>