[ 
https://issues.apache.org/jira/browse/AXIS2-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen resolved AXIS2-4309.
------------------------------------

       Resolution: Fixed
    Fix Version/s: post-1.5

I tried to fix this properly. Can you retest and reopen the issue if there are 
still problems? Thanks.

> JSONMessageFormatter isnt using the correct charset encoding
> ------------------------------------------------------------
>
>                 Key: AXIS2-4309
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4309
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>            Reporter: Johannes Wagener
>            Assignee: Andreas Veithen
>             Fix For: post-1.5
>
>
> When using JSONMessageFormatter, i had some trouble with german umlauts. The 
> response wasnt in the correct encoding (UTF-8)
> After debugging for while, i found out that getJSONWriter in 
> JSONMessageFormatter.java and JSONBadgerfishMessageFormatter.java
> is ignoring the requested charset encoding:
>     protected XMLStreamWriter getJSONWriter(OutputStream outStream) {
>         return new BadgerFishXMLStreamWriter(new 
> OutputStreamWriter(outStream));
>     }
> In my case outputStreamWriter was writing in CP819 (or something like that), 
> while the response had a   
> Content-Type: application/json;charset=UTF-8
> so i changed it to:
>     protected XMLStreamWriter getJSONWriter(OutputStream outStream,Charset 
> charset) {
>         return new BadgerFishXMLStreamWriter(new 
> OutputStreamWriter(outStream, charset));
>     }
> when calling getJSONWriter i used:
>  Charset charset = Charset.forName(format.getCharSetEncoding());              
>       
>  XMLStreamWriter jsonWriter = getJSONWriter(out,charset);
> and catching the UnsupportedEncodingException.
> After changing these 2 files, everything worked as expected.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to