The first child of the SOAP Body does not correspond to any of the operations defined in the specified WSDL definition.Ĭheck that the correct WSDL definition was deployed. : F:\build\slot1\S800_P\src\WebServices\WSLibrary\ImbSOAPParser.cpp: 1360: ImbSOAPParser::refreshBitStreamFromElementsInner: :īIP3602E: The Web service payload ''Input'' does not match an operation described by WSDL binding ''HelloWorldBinding'' in file ''dl''. Check that the SOAP logical supplied is correctly formatted. Review further error messages for an indication to the cause of the error. There is a problem with the SOAP logical tree format. : F:\build\slot1\S800_P\src\WebServices\WSLibrary\ImbSOAPReplyNode.cpp: 397: ImbSOAPReplyNode::evaluate: ComIbmSOAPReplyNode: Main#FCMComposite_1_2īIP3605E: The SOAP logical tree cannot be serialized. See previous error messages to determine the cause of the error. I got this:īIP3113E: Exception detected in message flow Main.SOAP Input (broker brk2)īIP3752E: The SOAP Reply node 'Main.SOAP Reply' encountered an error while processing a reply message.Īn error occurred during reply message processing. Somehow, things always out of expectation. The above WSDL shows the following request input: Ignore those unnecessary stuff, let's focus only on the input and output. Say I have a WSDL, which consist of following: Ever wonder how things done and I always got an excuse to delay my finding. It was the web service development on Message Broker. Just one small step will complete my finding.
0 Comments
Leave a Reply. |