Hi Marco
After testing a bit the service, I got to the following:
-
The output document contains a number of non-required child documents/fields
-
If the response does not contain one of those non-required fields, then it will not be correctly interpreted and the exception is thrown.
A workaround is filling those fields with “empty string”. Seems that the only important thing is that the elements are present in the SOAP response.
I suppose this is a bug somewhere (not necessarily in the WMMD code), cause those fields are defined as not required.
Hope this helps,
Javier
#webMethods#mobile#webMethods-General#Integration-Server-and-ESB