On Tuesday 31 October 2006 22:22, Filozof71 wrote: > Hello, > > That depends. WebServices are used in many context, usually as > integration solution. I have in specificationa that I should obtain > and send UTF-8 messages. My client is some legacy Windows > application, I assume pre-.net solution. >
What does your client use to decode the SOAP XML messages? If your client looks at the raw byte stream and does its own parsing of the XML (simple text pattern match for example) you are out of luck. You cannot expect Axis to work against clients which don't behave XML/SOAP spec compliant. > So the problem is what by default means UTF-8 encoded messages. > An UTF-8 encoded message is exactly that, each character being UTF-8 encoded. But using numeric character entities is perfectly legal in any XML document independent of its encoding. > Manuel, do you know how to switch off this conversation in Axis ? > I don't know of a switch to turn this off but this doesn't mean there is none. > sincerely Olek > > > ----- Original Message ----- > From: "Manuel Mall" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, October 31, 2006 1:50 PM > Subject: Re: Axis 1.4: Send dont't send string in UTF-8 > > > Just curious why you don't like the characters encoded as numeric > entities? Any decent XML parser should be able to handle that > correctly and return the correct Unicode code point for these > entities. > > Manuel > > > > --------------------------------------------------------------------- >- Jestes kierowca? To poczytaj! >>> http://link.interia.pl/f199e > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
