[jboss-user] [JBossWS] - Re: charset problem with jbossws 2.0.2 and .net clients

[EverlastX1]

I think I can't use the -Dfile.encoding=UTF-8  option because the 3rd party modules I am using don't work anymore if this option is on.


Am I right if I say that normally the conversation should be done automatically upon receive of the elements?

it is working in the forward direction
.NET (latin1) (auto convert to utf-8) |--->transport channel ( in utf-8)--->| (auto convert to latin1) jboss (Latin1)

but not in the backward direction (how I expected it would be)
.NET (latin1) (auto convert to latin1) |<---transport channel (in utf-8)<---| (auto convert to utf-8) jboss (Latin1)

what really happens is this: (you can see it from my first ans second post)
.NET (latin1) (auto convert to latin1) |<---transport channel (in utf-8)<---| (second time convert to utf-8)(auto convert to utf-8) jboss (Latin1)

result is = one utf-8 conversation needed on the .net Side



Is there any other way to solve this problem then this option with -D-Dfile.encoding=UTF-8 ?

thank you for help

Best Regard 

Vadim





View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4117558#4117558

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4117558