WBI SOAP response - accented characters missing

[Satish]

Hi Gurus,
Please help me in this, I have tried all options available to me.

(Option 1)
I am making a simple request from VB.NET client to WBI generated WSDL and
passing request parameters. The response I am expecting should have some
accented characters (Customer Name: Lokalcenter Åbygård), but this gets
truncated and response is as follows (Customer Name: Lokalcenter bygrd). The
WSDL has utf-8 character set defined.

Here is my VB.NET code:

'Making Direct call to WBI exposed web service WSDL
Dim wbiOrderRqst As New WbiWS.SERVICE_SYNCH_OrderDetails_Content_Request
wbiOrderRqst.SalesOrderNumber = "5831"

Dim wbiOrderRspns As New WbiWS.SERVICE_SYNCH_OrderDetails_Content_Response
Dim wbiOrderSubmit As New WbiWS.SERVICE_SYNCH_OrderDetails

'Pass request parameter and wait for response here
wbiOrderRspns = wbiOrderSubmit.requestOrderDetails(wbiOrderRqst)

(Option 2)
I tried testing the same request/response using Mindreef's - SOAPscope (Web
services diagnostics tool), in this case the response what I get is (Customer
Name: Lokalcenter �byg�rd)

(Option 3)
Then I tried testing the same request/response using "HTTP Watch" tool, the
response is as follow (Customer Name: Lokalcenter �byg�rd)

What is the problem here or what mistake I am doing?

Appreciate your early response.
--
Thanks and regards,
- Satish :)

[Kevin Yu [MSFT]]

Hi Satish,

We have reviewed this issue and are currently researching on it. We will
update you ASAP. Thanks for your patience!

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[[MSFT]]

Hello Satish,

From Option 2&3, it seems accented characters have been sent to client.
(Only Sent, we cannot guarantee it was sent correctly since they gave wrong
results in SOAPscope and HTTP Tool.) In VB code, the issue was related to
how the client code handle the SOAP ot HTTP message, for example decoding
and serialization. The accented characters may be ignored during these
process.

I am not familar with WBI. I suggest you may contact vendor to see if they
can provide detail information about how their client handle these message
and accented characters. With these information, we may work out this issue.

Luke

[Satish]

Hi Luke,

You mentioned ...
"In VB code, the issue was related to how the client code handle the SOAP ot
HTTP message, for example decoding and serialization. The accented characters
may be ignored during these process."

So, does that mean, am I missing any step in my VB code like decoding, etc?
Because if you look at my code (see in-line comments below):

'Creating an request object here
Dim wbiOrderRqst As New WbiWS.SERVICE_SYNCH_OrderDetails_Content_Request
'Passing value to request object
wbiOrderRqst.SalesOrderNumber = "5831"

'Creating response object
Dim wbiOrderRspns As New WbiWS.SERVICE_SYNCH_OrderDetails_Content_Response
'Creating submit object
Dim wbiOrderSubmit As New WbiWS.SERVICE_SYNCH_OrderDetails

'Pass request parameter and wait for response here
wbiOrderRspns = wbiOrderSubmit.requestOrderDetails(wbiOrderRqst)

So, is that before getting the response, do I have to do something, which I
am missing?

Kindly let me know ASAP.

Thanks and regards,
"[MSFT]" wrote:

Hello Satish,

From Option 2&3, it seems accented characters have been sent to client.
(Only Sent, we cannot guarantee it was sent correctly since they gave wrong
results in SOAPscope and HTTP Tool.) In VB code, the issue was related to
how the client code handle the SOAP ot HTTP message, for example decoding
and serialization. The accented characters may be ignored during these
process.

I am not familar with WBI. I suggest you may contact vendor to see if they
can provide detail information about how their client handle these message
and accented characters. With these information, we may work out this issue.

Luke

[[MSFT]]

Hello Satish,

For a normall web service, we only need simple code like what you have
done. However, most work (like decoding and serialization) will be done by
the proxy class and we don't know what happened in it. To trouble shoot the
problem , you may need debug into the function "requestOrderDetails", to
see what happened in it. Unfortunetely, I have no idea about it because I
am not a professional on WBI. You have better consult a WBI professional
for this issue.

Luke