OLD FORUM - Use new one: https://www.CaptainCasa.online/forum

Hello Björn,

we switched from Casabac release 13.04.2010 to the actual release 18.10.2010.

Now we have some problems with äöü, when we are calling a web service via ClientHttpSender.

For instance: We want to transfer the name 'Jörg Möller' in an xml stucture.

With release 13.04.2010 the following xml data are transferred with escaped ö.

<KAHA_NAME>Möller</KAHA_NAME>
<KAHA_VORNAME>Jörg</KAHA_VORNAME>

In the sample above the ö is escaped in a correct way.

But with release 18.10.2010 the ö is escaped incorrectly.

<KAHA_NAME>M&#246;ller</KAHA_NAME>
<KAHA_VORNAME>J&#246;rg</KAHA_VORNAME>

The & is now transferred as & and the result is that the receiving application displays 'Jörg Möller' instead of 'Jörg Möller'

With release 04.10.2010 the handling of '&' has changed.

May be this is the cause for the problem of sending äöü via ClientHttpSender.

Can you reproduce my äöü problem, Björn?

Hi,

yes, we did some correction in this area (ChangeLog for 20101004). We are just checking your scenario + come back to you.

Björn

Hi,

the behavior has changes in this area but is "more correct" then it was before...

Before a String "ö" was transferred to "ö" when it was sent from the client to the server. Now "ö" is received in the client as "ö". So, there is no "loss of data" anymore.

Who is building the "&#xxx;" in your application - is it something you received from another system? I'll try to call you directly...

Björn

....exactly the same "loss of information" happened with my previous post that we are just talking about...

Before "ö" was transfferred to "ö", this is what I wanted to say...

Björn

Hi Björn,

mea culpa. It was my fault.

My xml was not properly created.

Now i use ValueManager.encodeIntoValidXml (as you suggested) to set the attributes of my xml object.

Now everything is okay with öäü.

Thank you very much for your help!

Joe