Sergey thanks for the reply.
Adding the @Encoded on the path parameter results in the parameter to be
assigned the encoded value ie.
%D0%A2%D0%B5%D1%81%D1%82%20%D0%A2%D0%B5%D1%81%D1%82
In the end I looked at my log file type and it was not UTF-8 hence I added
the following to make it UTF-8
In addition, my editor (TextPad) doesn't show UTF-8 so I swapped to
Notepad++ that it does and by also removing the @Encoded annotation I got
the "Тест Тест"
Now the value is correctly retrieved from JAX-RS and passed to my JAX-WS
Client Adapter (all the way the log shows that) and it is also sent
correctly in the SOAP request (loginterceptors show this in the printout of
the SOAP Request whilst the fact that the external web service now replies
seems to confirm it).
The problem that remains is that when I receive a response that contains
Bulgarian characters both the log and the REST client do not get the correct
character encoding however the same request in SOAP UI results in the
correct character display
> The issue can be seen in the (My Log and my Rest Client get these)
>
> <City>Р?Р°С?РЅР°</City>
> <Address>жк. Чайка</Address>
>
> whilst in SOAPUI the result is correct
> <City>Варна</City>
> <Address>жк. Чайка</Address>
the headers for the response I receive are. I thought the ISO-8859-1 may be
affecting me but then again not certain why SOAP UI handles it correctly. As
far as I see I cannot influence the encoding returned by the web service
itself from my conduit.
> ID: 2
> Response-Code: 200
> Encoding: ISO-8859-1
> Content-Type: text/xml
> Headers: {Content-Length=[1011], content-type=[text/xml],
> Server=[IRS/1.0.18.0 guz]}
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Client-Problem-with-Encodings-tp5714097p5714141.html
Sent from the cxf-user mailing list archive at Nabble.com.
