In fact, I've changed both of them.
By default, th encoding is ISO-8859-1 in the soap Message (with NuSoap).
I can see it using TCPMonitor (Axis) to see my request and my response
If y change the message encoding to UTF-8, the web service still send the
letters in the soap message.
But I don't think that the problem is on the server side.
The fact is that WSE2.0 doesn't support special letters and I would like it
to support them.
> You changed your http server's encoding settings, NOT the encoding of
> the SOAP message (out on a limb here because I don't use Apache nor PHP
[quoted text clipped - 9 lines]
> OT: Using SoapEnvelope, you can specify the (request)encoding, by
> manually setting the SoapEnvelope.Encoding property.
Yves Reynhout - 25 Mar 2005 00:50 GMT
> The fact is that WSE2.0 doesn't support special letters and I would like it
> to support them.
This is downright untrue. I can send you a project using both asmx and
WSE 2.0 (both client and server, both .NET), that can send é over UTF-8.
Drop me an email at yves.reynhout@nospam.com (replace the nospam with
ultragenda - just hate getting spam).
It has nothing todo with WSE 2.0, but with the encoding on your xml
payload and how your xml payload was encoded.