man068
asked on
utf-8 converted to garbage ?? in SoapHttpClientProtocol
Hi,
We use .NET client to connect weblogic 7.1 server. I used the wsdl.exe to generate the proxy classes for wsdl file from weblogic. When I use this service to send the extended ascii characters from .NET client such as é it goes to weblogic server fine. Its fine in the response as well, but when the .NET regenerates the client proxy objects, it becomes "??". When I print out the xml its generating from proxy object it says its using "utf-8" encoding, but seems like its screwing up the data when it comes back from the server, ie., its using utf-16 instead. Has anybody faced such a problem.
thanks in advance.
We use .NET client to connect weblogic 7.1 server. I used the wsdl.exe to generate the proxy classes for wsdl file from weblogic. When I use this service to send the extended ascii characters from .NET client such as é it goes to weblogic server fine. Its fine in the response as well, but when the .NET regenerates the client proxy objects, it becomes "??". When I print out the xml its generating from proxy object it says its using "utf-8" encoding, but seems like its screwing up the data when it comes back from the server, ie., its using utf-16 instead. Has anybody faced such a problem.
thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have requested this question tobe deleted, so please dont post comments/answers.