Hi all,
my legacy server called by an axis2/J web service code passes an returns
to axis2 a long xml string.
This string is completed in the web service (Java code) and then
converted to an AXIOM OMElement type.
When the legacy server returns a <FF>, areal form feed character, Ascii
Code 12, then something goes wrong and my .NET WCF 3.5 stub returns the
error message to VB
"The remote server returns an unexpected response: (400) Bad
Request.
However, I know that my legacy server works with ISO-LATIN 8859-1 and
that Axis2 and/or Java likes UTF-8.
Hence I call the Axis2/C Isolatin2UTF8 routine before I return the
string to the Java Web Service part.
that to say; we make sure that only UTF-8 is give as response by the
legacy server code to the web service
In the java Web Service Part this <FF> char is not converted because
there is no need to convert it;
this conforms to the UTF-8 standard which says that any 7 bit character
does not need to be converted and that such 7 bit values are the same in
UTF-8
So any clue what goes wrong?
We use SOAP/XML over a HTTP Transport.
Taking out the <FF> from the text we intend to transfer back to the
VB/#C/.NET/WCF 3.5 client and all is OK.
Josef
