I’m invoking a method on a 3rd party webservice using a WCF service client.
Everytime I invoke the method from code, no error occurs but my response
object is NULL.
Examining the reponse in fiddle shows me a response
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Wed, 06 Jan 2010 14:30:12 GMT
143f
<?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”><CONTENT…></soapenv:Envelope>
0
The response has a header of encoding chunked. The only thing I can find on
the internet is that WCF does not support this.
I have been playing around with the messageEncoding (Mtom etc.) and
transferMode (Buffered) settings of the client config but no result.
I tried it using a 2.0 web service client proxy, and then it works.
Any idea’s how to resolve this.
|
|
0
|
|
|
|
Reply
|
Utf
|
1/11/2010 11:12:02 AM |
|
If it say it succeeded, it likely really did succeed.
Try http protocol, I don't see why this should fail if web services is
working. Perhaps it is the way you cast the returned object? Show so code.
--
Vapordan
Shameless Author Plug
ASP.NET 4 by Example only $20
OWC Blackbook www.lulu.com/owc
"Martijn van Schie" <mvanschie@newsgroup.nospam> wrote in message
news:D56626F7-F27F-4A1A-B899-43BD9DC91825@microsoft.com...
> I’m invoking a method on a 3rd party webservice using a WCF service
> client.
> Everytime I invoke the method from code, no error occurs but my response
> object is NULL.
> Examining the reponse in fiddle shows me a response
>
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Type: text/xml;charset=utf-8
> Transfer-Encoding: chunked
> Date: Wed, 06 Jan 2010 14:30:12 GMT
>
> 143f
> <?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”><CONTENT…></soapenv:Envelope>
> 0
>
> The response has a header of encoding chunked. The only thing I can find
> on
> the internet is that WCF does not support this.
>
> I have been playing around with the messageEncoding (Mtom etc.) and
> transferMode (Buffered) settings of the client config but no result.
>
> I tried it using a 2.0 web service client proxy, and then it works.
>
> Any idea’s how to resolve this.
>
|
|
0
|
|
|
|
Reply
|
Alvin
|
1/11/2010 4:21:16 PM
|
|