Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 5.3
edited by Elena
on 2025/06/17 14:34
Change comment: There is no comment for this version
To version 3.1
edited by Helena
on 2025/05/27 13:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.elenasemanticproorg
1 +xwiki:XWiki.helena
Tags
... ... @@ -1,1 +1,0 @@
1 -Attribute|Code|Statistical data and metadata exchange
Content
... ... @@ -34,7 +34,7 @@
34 34  
35 35  [[image:1748343115246-390.png]]
36 36  
37 -The XML is passed to the XmlSerializer to de-serialize it into the instances of classes in managed [[code>>doc:sdmx:Glossary.Code.WebHome]] that map to the input parameters for the Web method. Likewise, the output parameters and return values of the Web method are serialized into XML in order to create the body of the SOAP response message.
37 +The XML is passed to the XmlSerializer to de-serialize it into the instances of classes in managed [[code>>doc:sdmx:Glossary.Code.WebHome]] that (% style="color:#e74c3c" %)map(%%) to the input parameters for the Web method. Likewise, the output parameters and return values of the Web method are serialized into XML in order to create the body of the SOAP response message.
38 38  
39 39  In case the developer wants more control over the serialization and de-serialization process a solution is represented by the usage of **XmlElement** parameters. This offers the opportunity of validating the XML against a schema before de-serializing it, avoiding de-serialization in the first place, analyzing the XML to determine how you want to de-serialize it, or using the many powerful XML APIs that are available to deal with the XML directly. This also gives the developer the control to handle errors in a particular way instead of using the faults that the XmlSerializer might generate under the covers.
40 40