WSDL SOAP Analyzer

[jgarrison]

I get

org.apache.commons.httpclient.HttpException :
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instan ... ody><Fault xmlns="http://schemas.xmlsoap.org/soap/envelope/"><faultcode xmlns="">Server.generalException</faultcode><faultstring xmlns=""><![CDATA[org.xml.sax.SAXException: WSWS3084E: Error: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.]]></faultstring><detail xmlns=""/></Fault></soapenv:Body></soapenv:Envelope>

trying to use the SOAP analyzer against a web service. From the exception it appears that this is occurring locally but I can't be sure. Is this a known problem in OxygenXML? I can successfully access this service in other tools (Lombardi Teamworks, for instance).

[Radu]

Hi,

The error you encountered comes from the server side of the IBM WebSphere Application Server:

Code: Select all

 WSWS3084E: Error: {0} encountered a child element, which is NOT expected, in something it was trying to deserialize.

Explanation: This message normally indicates that the soap message is invalid. The engine was expecting a simple value when it encountered a child element. The soap message cannot be deserialized.

User Response: For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.

In conclusion, there is probably an XML tag in the sent XML SOAP message which the server expects to have a simple value but finds other tags inside it.
In order to try and see if Oxygen could compose a better XML SOAP message for the operation we would need the WSDL file you are using and also if you could send us the XML SOAP message generated with the tool which succesfully communicates with the server. If you can make this information available you can send it to us at support at oxygenxml dot com


Best regards,
Radu

[jgarrison]

Never mind, I was able to figure out the problem.

The providers of the web service don't have a clue.

The parameters are defined as string types, but they're expecting xml. I was providing unescaped xml, but since the types are strings, the xml has to be escaped. Why they didn't specify the expected xml schema as part of the wsdl is beyond me.