Skip to Content
Last modified by Artur on 2025/09/10 11:19
From version 1.4
edited by Helena
on 2025/05/27 13:52
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
Content
... ... @@ -52,14 +52,16 @@
52 52  
53 53  The difference between the two is that for the first method, **SubmitXml**, the XmlSerializer will expect an element named **input** to be an immediate child of the **SubmitXml** element in the SOAP body. The second method, **SubmitXmlAny**, will not care what the name of the child of the **SubmitXmlAny** element is. It will plug whatever XML is included into the input parameter. The message style from ASP.NET Help for the two methods is shown below. First we look at the message for the method without the **XmlAnyElement** [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
54 54  
55 -[[image:1747854163928-581.png]]
55 +[[image:1748343180527-572.png]]
56 56  
57 57  Now we look at the message for the method that uses the **XmlAnyElement** [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]].
58 58  
59 -[[image:1747854190641-364.png]]
60 60  
61 -[[image:1747854236732-512.png]]
60 +[[image:1748343195709-593.png]]
62 62  
62 +[[image:1748343209556-271.png]]
63 +
64 +
63 63  The method decorated with the **XmlAnyElement** [[attribute>>doc:sdmx:Glossary.Attribute.WebHome]] has one fewer wrapping elements. Only an element with the name of the method wraps what is passed to the **input** parameter.
64 64  
65 65  For more information please consult: [[http:~~/~~/msdn.microsoft.com/en-us/library/aa480498.aspx>>http://msdn.microsoft.com/en-us/library/aa480498.aspx]]
... ... @@ -66,12 +66,10 @@
66 66  
67 67  Furthermore at this point the problem with the different requests has been solved. However there is still the difference in the produced WSDL that has to be taken care. The automatic generated WSDL now doesn’t insert the extra element, but defines the content of the operation wrapper element as “xsd:any” type.
68 68  
69 -[[image:1747854286398-614.png]]
71 +[[image:1748343238333-226.png]]
70 70  
71 -Without a common WSDL still the solution doesn’t enforce interoperability. In order to
73 +Without a common WSDL still the solution doesn’t enforce interoperability. In order to “fix” the WSDL, there two approaches. The first is to intervene in the generation process. This is a complicated approach, compared to the second approach, which overrides the generation process and returns the envisioned WSDL for the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Web Service.
72 72  
73 -“fix” the WSDL, there two approaches. The first is to intervene in the generation process. This is a complicated approach, compared to the second approach, which overrides the generation process and returns the envisioned WSDL for the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Web Service.
74 -
75 75  This is done by redirecting the request to the “/Service?WSDL” to the envisioned WSDL stored locally into the application. To do this, from the project add a “Global Application Class” item (.asax file) and override the request in the “Application_BeginRequest” method. This is demonstrated in detail in the next section.
76 76  
77 77  This approach has the disadvantage that for each deployment the WSDL end point has to be changed to reflect the current URL. However this inconvenience can be easily eliminated if a developer implements a simple rewriting module for changing the end point to the one of the current deployment.
... ... @@ -80,27 +80,28 @@
80 80  
81 81  In the context of the [[SDMX>>doc:sdmx:Glossary.Statistical data and metadata exchange.WebHome]] Web Service, applying the above solution translates into the following:
82 82  
83 -[[image:1747854385465-132.png]]
83 +[[image:1748343320957-784.png]]
84 84  
85 85  The SOAP request/response will then be as follows:
86 86  
87 87  **GenericData Request**
88 88  
89 -[[image:1747854406014-782.png]]
89 +[[image:1748343334141-710.png]]
90 90  
91 91  **GenericData Response**
92 92  
93 -[[image:1747854424488-855.png]]
94 94  
94 +[[image:1748343349364-875.png]]
95 +
95 95  For overriding the automatically produced WSDL, in the solution explorer right click the project and select “Add” -> “New item…”. Then select the “Global Application Class”. This will create “.asax” class file in which the following [[code>>doc:sdmx:Glossary.Code.WebHome]] should replace the existing empty method:
96 96  
97 -[[image:1747854453895-524.png]]
98 98  
99 -[[image:1747854476631-125.png]]
99 +[[image:1748343378195-828.png]]
100 100  
101 -The SDMX_WSDL.wsdl should reside in the in the root directory of the application. After applying this solution the returned WSDL is the envisioned. Thus in the request message definition contains:
102 102  
103 -[[image:1747854493363-776.png]]
102 +[[image:1748343367090-262.png]]
104 104  
104 +The SDMX_WSDL.wsdl should reside in the in the root directory of the application. After applying this solution the returned WSDL is the envisioned. Thus in the request message definition contains:
105 105  
106 -{{putFootnotes/}}
106 +
107 +[[image:1748343398861-686.png]]
1748343180527-572.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +29.6 KB
Content
1748343195709-593.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +31.4 KB
Content
1748343209556-271.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +2.0 KB
Content
1748343238333-226.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +15.5 KB
Content
1748343320957-784.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +9.6 KB
Content
1748343334141-710.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +28.8 KB
Content
1748343349364-875.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +30.7 KB
Content
1748343367090-262.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +22.6 KB
Content
1748343378195-828.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +833 bytes
Content
1748343398861-686.png
Author
... ... @@ -1,0 +1,1 @@
1 +xwiki:XWiki.helena
Size
... ... @@ -1,0 +1,1 @@
1 +16.1 KB
Content
SUZ.Methodology.Code.MethodologyClass[0]
index
... ... @@ -1,0 +1,1 @@
1 +11