Also just wanted to show what the TCP monitor is howing for the response
<?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Body/> </soapenv:Envelope> So the body elemet is empty and the wsdl snippet is below: <message name="AddrMessage"> <part name="input" element="inx:Address" /> </message> <message name="AddrMessageResponse" /> <portType name="AddrPortType"> <operation name="processAddr"> <input message="inws:AddrMessage" /> <output message="inws:AddrMessageResponse" /> </operation> </portType> Note the AddrMessageResponse definition - thats empty too. So can I conclude that an empty wsdl"message definition would imply a empty soap body element in wire? thanks Rishi On 3/30/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
On 3/29/07, Rishi krish <[EMAIL PROTECTED]> wrote: > > Hi All > This is probably a generic wsdl question - I will be using a the Axis2 > serviceclient api to call a web service which has a wsdl operation [with > http binding] the outpout of which refers to a wsdl:message which has no > parts defined. I am wondering what that means for the service response? > http binding has not clearly defined in wsdl 1.1. so if you deal with http bindings better to use WSDL 2.0 A>the response would be an empty soap body > if you use http binding you would not get any soap messages. So we can throw this option. Actually this is the case if you have above serario with a document/literal binding. B>The response would be just an http response with no trace of soap. [no > soap envelope] > I think this should be the case. the problem here is that wsdl 1.1 spec does not clearly specify whether we have to use the rpc type message construction or document type message construction with http binding. Can anyone pls confirm what should be the response if the service/soap > engine is behaving correctly? > > -- > thanks > Rishi > -- Amila Suriarachchi, WSO2 Inc.
-- thanks Rishi
