Phil,

Currently, there are no more encoding issues that I know off. Could you create a minimal SA that demonstrates the problem or a failing unit test and attach it to a new JIRA issue, so we can look into it?

Thank you,

Gert

Philip Webster wrote:
Hi,
I've just tried apache-servicemix-3.2-20071025.000703-20, and I still have
the same problem.

Are there any other open bugs concerning encoding that might be the cause?

Phil



Gert Vanthienen wrote:
Phil,

Not entirely sure about it, but you might be running into https://issues.apache.org/activemq/browse/SM-1114, which has only been solved very recently.
Would it possible to retry your use case with a recent build from trunk?

Regards,

Gert

Philip Webster wrote:
I'm using Red Hat Linux on the server, and the terminal supports Unicode.
The
debug logging that I display in the terminal looks correct.

I have also tried running ServiceMix under Windows XP Professional, and
on
that the output is wrong. This seems to be because the Windows command
prompt window is not displaying unicode output.

Regardless, the output received by the web services client is wrong.

Phil




Carl23 wrote:
What platform are you running ServiceMix on?

Carl


Philip Webster wrote:
<Title>Meñiquín Charles Perrault ; traducción de Teodoro
Baró</Title>
instead of:
<Title>Meñiquín Charles Perrault ; traducción de Teodoro Baró</Title>

The results are unreadable. I've checked the input files, and they are
all correct and readable. I've checked the output from the search
engine
that I am calling (this is outside ServiceMix), and that is also
correct
and readable.

There is a lot of logging in my code, and the output from that also has
the correct characters in it. At this point we are within ServiceMix,
and
everything seems to be fine. However, once the results are sent out of
the HTTP-SU, I get these incorrectly encoded results.

The search engine uses stubs to call another, non-servicemix web
service,
then processes and repackages the results in a JSR-181 service unit.
The
methods in the JSR181-SU are invoked via web service calls through a
HTTP-SU.
It looks as though there is an encoding problem at the point after the
results are returned from the JSR181 service unit. Is there a
configuration option in the HTTP-SU that I need to change to enable
unicode? Is this a bug?




Reply via email to