I found the problem. It had to do with my client, not ServiceMix! Sorry.
Anyway, I'll point out this detail regarding reading HTTP BC UTF-8 output
(client side):
Socket socket = new Socket(addr, port);
Charset charset = Charset.forName("UTF-8");
BufferedReader rd = new BufferedReader(new
InputStreamReader(socket.getInputStream(),charset.newDecoder()));
This is the part of the code that correctly decodes UTF-8 for me. I was
using something similar, but without the Charset defined in the
InputStreamReader constructor, and UTF-8 special characters (like ã or ç)
were corrupted.
Hope this helps someone!
wizard wrote:
>
> Yes, I forgot to add, I was using 3.1 (recent snapshots) and right now I'm
> using the new release.
>
>
> gnodet wrote:
>>
>> Some bugs have been fixed in 3.1. Do you use this version ?
>>
>> On 2/12/07, wizard <[EMAIL PROTECTED]> wrote:
>>>
>>> I'm using a HTTP and FILE Binding Components to send Messages to my
>>> Service
>>> Engines.
>>>
>>> When I send my messages (xml) through the file component, the SE
>>> receives
>>> them OK. When I send the same messages through the HTTP BC the special
>>> characters like: ç or ã get corrupted. I'm using UTF-8 everywhere
>>> (sockets,
>>> xml message, file encoding, etc...)
>>>
>>> Why is this happening with the HTTP BC?
>>> --
>>> View this message in context:
>>> http://www.nabble.com/HTTP-BC-and-UTF-8-tf3216721s12049.html#a8933425
>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Architect, LogicBlaze (http://www.logicblaze.com/)
>> Blog: http://gnodet.blogspot.com/
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/HTTP-BC-and-UTF-8-tf3216721s12049.html#a9001454
Sent from the ServiceMix - User mailing list archive at Nabble.com.
