Re: wsdl message with no parts

2007-04-03 Thread Anne Thomas Manes
I assume that MXPERSONTinterface is defined in the imported schema. From what I see, the WSDL is WS-I BP 1.1 compliant. My assumption is that the .NET validator has a bug. Anne On 4/3/07, Rishi krish <[EMAIL PROTECTED]> wrote: Hi Anne I am attaching the wsdl and the conformance report as well

Re: wsdl message with no parts

2007-04-02 Thread Anne Thomas Manes
.NET can consume an unwrapped doc/literal service, but it's less convenient for the .NET developer. As a general rule, I recommend that you always follow the wrapped convention. I'm having trouble understanding where the BP 1.1 validator is failing. Could you show us the WSDL (or a similar repres

Re: wsdl message with no parts

2007-04-01 Thread Rishi krish
Hi Anne Thanks again for your clarification on .Net requirements. You said doc-Lit wrapped is the *default* format generated by .Net. Do you imply that if my axis service is not conforming to doc-lit wrapped format .Net cannot communicate to it? OR .Net can be configured to communicate with a serv

Re: wsdl message with no parts

2007-04-01 Thread Anne Thomas Manes
One more thing ... The wrapped convention also requires that the response element be defined as a complexType with a sequence, e.g., If you have an empty message, then you aren't following the wrapped convention. The wrapped convention requires that the input message contain an element whose lo

Re: wsdl message with no parts

2007-04-01 Thread Anne Thomas Manes
If you have an empty message, then you aren't following the wrapped convention. The wrapped convention requires that the input message contain an element whose local name is the same as the operation, and the output message contain an element whose local name is the operation appended with "Respon

Re: wsdl message with no parts

2007-03-31 Thread Rishi krish
Hi Anne thanks for the clarification. I am wondering if what you said for RPC type is also valid for the wrapped doc-lit type too [which kind of similar to rpc literal type and which is followed by .Net]. I mean if a pojo service method signature reads -- public void test(String s) The response

Re: wsdl message with no parts

2007-03-31 Thread Anne Thomas Manes
It depends on the style. If you are using document style, an empty message declaration with no parts (either input or output) will generate an empty SOAP body. If you are using rpc style, an empty input message declaration will generate a SOAP body containing an element that has a local name equ

Re: wsdl message with no parts

2007-03-30 Thread Rishi krish
Also just wanted to show what the TCP monitor is howing for the response http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance";> So the body elemet is empty and the wsdl snippet is below:

Re: wsdl message with no parts

2007-03-30 Thread Rishi krish
Hi Amila I am sorry for confusing the qustion. I am WSDL is using soap binding with http as the transport protocol. In my secnario the WSDL operation has both intput and output message and the output message has no part associated with it. My question was should the service response contain an emp

Re: wsdl message with no parts

2007-03-29 Thread Amila Suriarachchi
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 w

wsdl message with no parts

2007-03-29 Thread Rishi krish
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? A>