Loading ...
Sorry, an error occurred while loading the content.

RE: [soaplite] SOAP::Lite server and .NET client

Expand Messages
  • Khamesra, SandeepX
    You are correct..Actually I was using a wrong attribute for building envelop.. This I fig. out when I actully generated a proxy stub from the WSDL file Any way
    Message 1 of 4 , May 2 2:59 PM
    • 0 Attachment
      You are correct..Actually I was using a wrong attribute for building
      envelop.. This I fig. out when I actully generated a proxy stub from the
      WSDL file

      Any way thx a lot for to all for help .



      -----Original Message-----
      From: Duncan Cameron [mailto:dcameron@...]
      Sent: Thursday, May 02, 2002 1:53 PM
      To: Khamesra, SandeepX
      Subject: Re: [soaplite] SOAP::Lite server and .NET client


      On 2002-05-01 Khamesra, SandeepX wrote:
      >I have .NET Server , .NET client and SOAP::Lite server
      >When I talked from .NET client to .NET server , I get the expected out put
      >but when same .NET client talks to SOAP::Lite server though the wire
      >dumplooks the same but client is not able to extract the data..

      The wire dumps are not the same - see below. It looks as if you need to
      ensure that
      all elements are in the correct namespace.. This is one of the things which
      the
      SOAP::LIte documentation poinst out.

      >..NET Client and SOAP::Lite Server
      .. snipped ...

      ><?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope
      >
      >xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
      >
      >SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
      >
      >xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
      >
      >xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
      >
      >xmlns:xsd="http://www.w3.org/1999/XMLSchema"><SOAP-ENV:Body><namesp1:sayHel
      l
      >oResponse
      >
      >xmlns:namesp1="urn:Hello"><sayHelloResult
      >
      >xsi:type="xsd:string">Sandeep</sayHelloResult></namesp1:sayHelloResponse></
      S
      >OAP-ENV:Body></SOAP-ENV:Envelope>
      >
      Here the <sayHelloResult> element is not in any namespace because it doesn't
      have a
      prefix and the default namespace has not been defined.


      >..NET Client and .NET Server

      .. snipped ...

      ><?xml version="1.0" encoding="utf-8"?><soap:Envelope
      >
      >xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
      >
      >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      >
      >xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><sayHelloResponse
      >
      >xmlns="urn:Example1"><sayHelloResult>Hello
      >
      >sandeep</sayHelloResult></sayHelloResponse></soap:Body></soap:Envelope>

      Here the <sayHelloResult> element is in the urn:Example1 namespace (because
      it doesn't
      have a prefix and the default namespace _has_ been defined)


      Regards,
      Duncan Cameron
    Your message has been successfully submitted and would be delivered to recipients shortly.