Well, it’s not actually part of the
SOAP protocol, but WS-I. But since WS-I is a very widely accepted standard for
interoperability (Axis 2 in many cases assumes you are WS-I compliant), it’s
best to follow those recommendations.
Brennan Spies
Sr. Programmer Analyst
Shared Application Services
-----Original Message-----
From: Bruno Negrao
[mailto:[EMAIL PROTECTED]
Sent: Wednesday,
November 01, 2006 10:28 AM
To: [email protected]
Subject: Re: Converting from UTF-8
to ISO-8859-I with Axis2 and Java
On 11/1/06, Spies, Brennan <[EMAIL PROTECTED]>
wrote:
"I haven't studied the specs to be able
to decide how it should work"...
Section 3.1.5 of the Simple SOAP Binding Profile (WS-I) states that
"Content-Type" HTTP header field-value must indicate the correct
character
encoding, using the "charset" parameter. In absence of this, it must
use the
default "us-ascii" charset. Furthermore, it says that the 'encoding'
attribute on the envelope should be ignored...
http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0.html#Character_Enco
dings
Brennan,
It seems you solved this thread. If these are the specifications of SOAP
protocol, Axis2 does not need any update, my SOAP server does.
I'll ask them to change it and if they do it i'll post the result here on this
thread.
Thank you,
bruno
