WCF: Text Message Encoding and ISO-8859-1 Encoding

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Paulo Morgado — Fri, 30 Oct 2009 09:25:45 GMT

I agree that WCF should support other encodings, but if you need something more than just calling a web service (security, other bindings (TCP, Pipes, etc.), logging, tracing, etc.) nothing beats WCF.

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Jim Rolph — Wed, 28 Oct 2009 23:44:49 GMT

I got this error too when using .NET 3.5/VS 2008. I added a "Service Reference" and imported the WSDL for a site driven by PHP. It built fine, but got the ISO-8859-1 encoding error.

I tried again after changing the project properties to uses .NET 2.0. This time, I was not offered the option of adding a "Service Reference", but I could add a "Web Reference". When I did that, everything worked fine.

Finally, I tried using .NET 3.5 again. I used "Add Service Reference" again, but this time I hit the "Advanced..." button. The next dialog box had a compatibility option where a button allowed you to add a "Web Reference" based on .NET 2.0 Web Services. This worked the same as when using .NET 2.0, but the rest of your app can use .NET 3.5.

There must be advantages in using the "Service Reference", but until WCF supports ISO-8859-1, using a "Web Reference" beats having to override IsContentSupported.

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Paulo Morgado — Sat, 29 Aug 2009 11:27:52 GMT

Hi Eric,

I'm not that good on WCF, but I think it could be done.

IsContentTypeSupported is a member of the MessageEncoder class. So you need one to override it.

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Eric Schlosser — Fri, 28 Aug 2009 22:04:49 GMT

Paul,

In the WSD Scan Spec, to retrieve a scan you send a standard utf-8 text message and recieve a mime type with enbedded MTOM in it. Since a basic wcf message can only send and recieve one type, could you use this to trap the content type mismatch? if so, without a custom message encoder can you use a IsContentTypeSupported overide and trap the mismatch?

Thanks in advance,

Eric

SOAP and DotNet 3.0 / 3.5 « Shaw Innes

SOAP and DotNet 3.0 / 3.5 « Shaw Innes — Thu, 09 Apr 2009 03:22:43 GMT

Pingback from SOAP and DotNet 3.0 / 3.5 « Shaw Innes

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Paulo Morgado — Thu, 07 Aug 2008 14:45:34 GMT

You are better of that way, but, at the time, I wasn't allowed that luxury.

Based on the sample, I wrote my onw message encoder and registered it and it without any change in both caller and called applications.

<?xml version="1.0"?>
<configuration>
<system.serviceModel>
   <bindings>
     <customBinding>
       <binding name="MyCustomBinding">
         <customTextMessageEncoding messageVersion="None" writeEncoding="ISO-8859-1" mediaType="text/xml" />
         <httpTransport manualAddressing="false" keepAliveEnabled="false" />
       </binding>
     </customBinding>
   </bindings>
   <client>
     <endpoint name="MyServiceEndpoint"
         address=http://myserver/MyPoxEndpoint
                 contract="IMyService"
                 binding="customBinding"
                 bindingConfiguration="MyCustomBinding" />
   </client>
</system.serviceModel>
</configuration>

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Erik — Thu, 07 Aug 2008 13:40:13 GMT

Thought WCF was there to make our lifes easier ;-)

For the moment fixed the problem at the other side: changed the PHP webservice so it returns UTF-8 and now it works.

I'll try to look at writing my own custom message encoder later.

Thanx for your reponse, made things clearer for me!

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Paulo Morgado — Wed, 06 Aug 2008 23:39:13 GMT

You have to do all that in order to WCF use your message encoder.

The message encoder will be called in by WCF while WCF runs the request/response through its pipeline.

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Erik — Wed, 06 Aug 2008 11:32:19 GMT

It's probably since I'm not yet familiar enough with .Net/WCF ;-)

But if I look at the artice I would have to write code for a custom MessageEncoder (where the IsContentTyepSupported is overridden), a custom

MessageEncoderFactory and a custom TextMessageEncodingBindingElement?

And I still cannot see where the custom MessageEncoder is actually hooked in when the call to the webservice is made.

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Paulo Morgado — Wed, 06 Aug 2008 11:05:56 GMT

Can you elaborate a bit more on where you need help here?

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Erik — Wed, 06 Aug 2008 09:36:13 GMT

Read the article, but still don't understand how easy I can implement this message encoder while calling such a webservice. Anyone any help?

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Paulo Morgado — Tue, 10 Jun 2008 16:26:28 GMT

See this article:

msdn.microsoft.com/.../ms751486.aspx

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Adam — Mon, 09 Jun 2008 22:49:46 GMT

So, this all makes sense to me, but for one thing: How do you configure your app to use your custom encoder containing the override?

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

Paulo Morgado — Sat, 09 Feb 2008 01:05:42 GMT

It can be on either side. Just put it where you need it to be.

re: WCF: Text Message Encoding and ISO-8859-1 Encoding

swapneel — Fri, 08 Feb 2008 07:23:42 GMT

where do we override this method, in the application. is it in the client side or in the service side.

XML SOAP Service: Encoding-Probleme - .NET Windows Forms @ tutorials.de: Forum, Tutorial, Anleitung, Schulung & Hilfe

Fri, 16 Nov 2007 14:01:47 GMT

Pingback from XML SOAP Service: Encoding-Probleme - .NET Windows Forms @ tutorials.de: Forum, Tutorial, Anleitung, Schulung & Hilfe

Optimizing reading for the CustomTextMessageEncoder

Paulo Morgado — Mon, 07 May 2007 20:45:32 GMT

Continuing the improvement of the CustomTextMessageEncoder (see this and this ), this time I'll use

WCF: Text Message Encoding and ISO-8859-1 Encoding

DotNetKicks.com — Wed, 25 Apr 2007 21:23:05 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com