On Jun 22, 2014, at 8:12 AM, Younes Ouadi younes.ou...@gmail.com wrote:
Hello Dears,
I'm stuck with the Async Client and accented characters. Please help.
Sorry, wasn’t clear. You need to use the HTTP transport based on the Apache
HTTP Components async clients. Some docs at:
Hi Younes,
yes. I think that would be a good approach.
If BizTalks is using the local charset, it can't even interoperate
with each other beyond the iso-latin-1 boarders.
That means, definitely they should consider changing the soapaction value.
regards, aki
2014-06-23 16:50 GMT+02:00 Younes
I think switching the encoding to iso-8859-1 won't solve the issue
because that won't be right.
all headers are supposed to be encoded in US-ASCII.
http://tools.ietf.org/html/rfc2822#page-7
Non ASCII values needed to be encoded using a special ASCII encoding
http://tools.ietf.org/html/rfc2047
We
Thank you @Aki for the clarification.
I'm now in a strong position to ask the people maintaining the third party
system to change their WSDL as it is using none standard implementation.
For your last question, I think BizTalk uses the local charset to encode
and decode the headers. The WSDL I'm
Hello Dears,
I'm stuck with the Async Client and accented characters. Please help.
As suggested by @Daniel, I have suitched to Async Client hoping to solve my
initial issue, that is: consuming a web service whose SOAPAction contains
an accented character.
To do so:
* I took the sample program
Hi @Daniel,
I appreciate very much your help. Thank you for the time, effort and
attention you have devoted to this question.
For your recommendation, I can't do much. The WSDL in question is already
in production consumed by a BizTalk-base client (the server is also a
BizTalk based server, as
Hello Dears,
I have an issue with soap-actions that contains accented charaters. I'm
sure that this is not something new and it is possible that I'm missing
something. So, please help.
My case is as follows:
* I have received a WSDL of a third party system
* I have used wsdl2java maven plugin to
Some bad news…. with a little bit of good news.
The HttpURLConnection that CXF uses by default for sending requests to the
server always seems to use UTF-8. I checked with Java 6/7/8 and they all do
that. There doesn’t seem to be any way to make it behave correctly. :-(
If you can try
Looking at the code for the JDK:
http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/6-b14/sun/net/NetworkClient.java#NetworkClient.0encoding
I see they intentionally leave it in whatever encoding it find with the
“file.encoding” system property at startup providing all the
