I found the same problem with Axis 1.4 but not sure about Axis2. In my case
the incoming SOAP included some CYRILIC characters which Axis 1.4 did not
recognise.

So I had to write a filter, modify the SOAP (replace chanracter greater than
146 by "&#" + c + ";") and pass the modified request to the filter chain.

This solved my purpose. Let me know if this solution suites your
requirement. I can share my code if you want.

Chinmoy



On Wed, Dec 2, 2009 at 5:41 PM, Vaibhav Arya
<[email protected]>wrote:

>
>
> *Hi All,*
>
> * *
>
> *I have a web-service developed in axis2. How can I make my web-service
> support UTF-8 encoding?*
>
> *It is not supporting special characters ((char) 199). And replacing it
> with the ‘?’ sign.  I presume that by setting the character encoding to
> UTF-8, this problem can be solved. But don’t know how to set character
> encoding? Can I use following…*
>
> * *
>
> *               *HttpServletRequest request = (HttpServletRequest)
> messageContext.getProperty (HTTPConstants.MC_HTTP_SERVLETREQUEST);
>
>
>
>                try{request.setCharacterEncoding("UTF-8");}catch(Exception
> encex){log4jcat.info("error while setting encoding UTF-8 :" +
> encex.toString());}
>
>
>
>
>
> Please suggest…
>
>
> ===================================================================================================
> Private, Confidential and Privileged. This e-mail and any files and
> attachments transmitted with it are confidential and/or privileged. They are
> intended solely for the use of the intended recipient. The content of this
> e-mail and any file or attachment transmitted with it may have been changed
> or altered without the consent of the author. If you are not the intended
> recipient, please note that any review, dissemination, disclosure,
> alteration, printing, circulation or Transmission of this e-mail and/or any
> file or attachment transmitted with it, is prohibited and may be unlawful.
> If you have received this e-mail or any file or attachment transmitted with
> it in error please notify OTS Solutions at [email protected]
>
> ===================================================================================================
>

Reply via email to