Hello Paul,

My idea was to search the SOAP header for a parameter like "charSet" defined
by the client to determine the encoding of the SOAP response which should be
independent from the encoding of the SOAP request.
Or is this idea completely rubish? Is Axis2 1.3 always responding with the
same encoding the client uses for the request?
The requirement is just to choose the encoding of the SOAP response at
runtime by the client. Some clients need utf-8, others need latin1. I don“t
know the best way to implement this. I cannot find notes on this topic in
the documentation.
When I take a look at the SOAP-Monitor, I see always utf-8 as encoding in
the XML header.

Jan

-----Original Message-----
From: Paul Fremantle [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 13, 2008 6:42 PM
To: [email protected]
Subject: Re: encoding of SOAP responses

Do you mean you need to use the same encoding as the client sent?

Paul

On Feb 13, 2008 5:35 PM, Jan Philipp Seng <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hello Rushikesh and Paul,
>
>
>
> thank you very much for your answers. Unfortunately my question was not
> precise enough. I am not consuming a web service, but offering it. Can I
> determine the encoding of the SOAP responses my server delivers at runtime
> depending on a parameter transmitted in the SOAP Header of the request
also?
>
>
>
> Thanks for your help,
>
> Jan



-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
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]

Reply via email to