Great,
I wouldn't never imagine that this flag is related to WS encoding,
Many thanks,
Asaf.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138763#4138763
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138763
__
Asaf,
We had the same problem. The problem occur because not all the steps that are
involved in Web Services creation support UTF-8 by default.
Add to your JBoss startup script the following parameter: -Dfile.encoding=utf-8
This should solve your problem.
Ronen
View the original post :
htt
Well, you could start investigating what actually goes to the wire to
understand which side is the problem. This way we could eventually see if
there's an issue and perhaps create a test case showing it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138293#4
Hey,
I performed some tests and now I am sure there's encoding problem but I'm not
sure on which size,
I've created the simplest WS .NET method with one string parameter and after
calling the WS method, on the .NET side I see gibberish instead of UTF8 encoded
string,
Please note, English wor
Hey,
Well, something is wrong,
I have a file saved as unicode, I read the content of the file into a java
String variable and pass it to the WS,
I see gibberish on the other side (C#),
Is there any way to investigate it? are there any WS testcases in C#/.NET and
WS client code in java so I c
javax.xml.soap.SOAPMessage
|/** Specifies the character type encoding for the SOAP Message. Valid
values include "utf-8" and "utf-16". The default is "utf-8". */
|public static final String CHARACTER_SET_ENCODING =
"javax.xml.soap.character-set-encoding";
|
The soap message can
