Hi Christian
Yes, they should.
The encoding issue is caused by we use String(byte[]) to handler the
String message. My fix will take out the content-type's charset to make
sure the JMS client and server are using the same encoding.
In this way we could avoid the issue of different default encoding
machine's talking.
BTW cxf 2.1.2 JMS transport does't send the content-type, and cxf 2.2
will take use the default encoding UTF-8, if there is no content-type
header in the JMS message.
Willem
Christian Schneider wrote:
> Btw. Have you tested if cxf 2.1.2 and 2.2-SNAPSHOT are still compatible
> regarding enconding?
> As far as I know the encoding problem was for 2.1.2 only if the client
> and server had different default locales. We should
> avoid creating headaches for businesses that do a step by step update of
> their servers from older cxf versions to the version that includes the
> encoding fix.
>
> Greetings
>
> Christian
>
> Willem Jiang schrieb:
>> Hi
>>
>> There is no {en|de}coding error when you talk in Germen :)
>> Can you try the CXF 2.1.4SNAPSHOT , which should include my patch of JMS
>> encoding[1] ?
>>
>> [1]https://issues.apache.org/jira/browse/CXF-1749
>>
>> Willem
>>
>> Christian Schneider wrote:
>>
>>> Hi Glen,
>>>
>>> I am putting a ü into the call :
>>> customers = customerService.getCustomersByName("Müller");
>>>
>>> Quite interesting is also that what the client sends is not the same as
>>> what the server receives:
>>> INFO: Outbound Message
>>> ---------------------------
>>> Encoding: UTF-8
>>> Headers: {SOAPAction=[""]}
>>> Messages: Payload: <soap:Envelope
>>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><ns2:getCustomersByName
>>>
>>> xmlns:ns2="http://customerservice.example.com/";><name>Müller</name></ns2:getCustomersByName></soap:Body></soap:Envelope>
>>>
>>>
>>> --------------------------------------
>>>
>>> INFO: Inbound Message
>>> ----------------------------
>>> Encoding:
>>> Headers: {SOAPJMS_contentType=[text/xml], SOAPAction=[""]}
>>> Messages: Message:
>>>
>>> Payload: <soap:Envelope
>>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><ns2:getCustomersByName
>>>
>>> xmlns:ns2="http://customerservice.example.com/";><name>M?ller</name></ns2:getCustomersByName></soap:Body></soap:Envelope>
>>>
>>>
>>> --------------------------------------
>>>
>>> The encoding is missing on the server side and the "ü" is diplayed as
>>> "?"
>>>
>>> btw. Drahthaifish is funny ;-)
>>> Greetings
>>>
>>> Christian
>>>
>>>
>>> Glen Mazza schrieb:
>>>
>>>> Christian Schneider wrote:
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> I am getting a CharconverionException when trying to receive a german
>>>>> character ü in a soap message.
>>>>> The error happens with cxf 2.1.3 with jms as transport. I have not
>>>>> tested on http yet. I am quite sure I did not see this exception when
>>>>> we worked on the snapshot.
>>>>>
>>>>> Any idea what is going wrong here? I have attached the log on the
>>>>> server and client side side. If it helps I can post the complete
>>>>> project.
>>>>>
>>>>> Greetings
>>>>>
>>>>> Christian
>>>>>
>>>>>
>>>> Hmmm. Vielleicht sollen Sie Drahthaifisch benützen, um zu versichern,
>>>> dass
>>>> Sie wirklich zu dem Dienst ein ü senden. Von Ihr SOAP-Anfrage unten
>>>> scheint
>>>> es, das Ihr sogenannte ü nicht wirklich ein ü ist.
>>>>
>>>> Hmmm. I would try Wireshark--you might not actually be sending a
>>>> u-umlaut
>>>> after all but another strange character instead. But you said
>>>> "receive"--i.e., from server to client--the problem seems to be with
>>>> your
>>>> *request* below, not response, correct? Could it be that a bad
>>>> request is
>>>> messing up your response?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Payload: <soap:Envelope
>>>>> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";><soap:Body><ns2:getCustomersByName
>>>>>
>>>>>
>>>>> xmlns:ns2="http://customerservice.example.com/";><name>M?ller</name></ns2:getCustomersByName></soap:Body></soap:Envelope>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
>>
>
>
