I just submitted it to JIRA:
http://nagoya.apache.org/jira/browse/AXIS-1682
thanks for the help.
Bernie
On Nov 23, 2004, at 6:58 PM, Davanum Srinivas wrote:
Looks like a useful change...can you please open a JIRA enhancement
request?
dims
On Tue, 23 Nov 2004 13:55:32 -0500, Bernie Bernstein
<[EMA
Bernie,
Looks like a useful change...can you please open a JIRA enhancement request?
thanks,
dims
On Tue, 23 Nov 2004 13:55:32 -0500, Bernie Bernstein
<[EMAIL PROTECTED]> wrote:
> I found a much easier way to do this by making only a minor
> modification to org.apache.axis.client.Call.java.
>
I found a much easier way to do this by making only a minor
modification to org.apache.axis.client.Call.java.
I added a new property:
public static final String CHARACTER_SET_ENCODING=
SOAPMessage.CHARACTER_SET_ENCODING;
and made the appropriate changes in the property checking code.
I managed to do it by copy/pasting some code from
org.apache.axis.client.Call.
It wasn't easy, but it involved creating a new Message object, setting
it's char encoding to "ISO-8859-1", and then assembling the envelope to
send to Call.
Then to deal with the response, the code needed to get the
We have a service set up which is working fine so far, but now our
client is requesting that we return our data in ISO-8859-1 instead of
UTF-8.
I've suggested that we stick with UTF-8 since it is more flexible, but
it seems that their system isn't able to handle UTF-8 for some reason.
In most
