old cxf attachment deserializer issue - causing it to not reset the message encoding to the encoding in the part

[Nicholas DiPiazza <ni...@gmail.com>]

this post http://www.mail-archive.com/users@cxf.apache.org/msg10711.html
says there was a bug in the attachment deserializer that was causing it to
not reset the message encoding to the encoding in the part.

 

I'm experiencing this issue. Does anyone have any knowledge of this problem?


 

When we send an XML document in a SOAP response as an MTOM attachment, the
encoding changes from UTF-8 to ISO-8859-1. 

 

We've isolated that it happens in
ServiceInvokerInterceptor.handleMessage(Message)

 

Anyone ever see this happen before? 

 

-Nicholas 

 

Re: old cxf attachment deserializer issue - causing it to not reset the message encoding to the encoding in the part

[Jason Pell <ja...@pellcorp.com>]

I am sure the first question will be what version of cxf are you using?



On Tue, Feb 12, 2013 at 6:12 AM, Nicholas DiPiazza
<ni...@gmail.com> wrote:
> this post http://www.mail-archive.com/users@cxf.apache.org/msg10711.html
> says there was a bug in the attachment deserializer that was causing it to
> not reset the message encoding to the encoding in the part.
>
>
>
> I'm experiencing this issue. Does anyone have any knowledge of this problem?
>
>
>
>
> When we send an XML document in a SOAP response as an MTOM attachment, the
> encoding changes from UTF-8 to ISO-8859-1.
>
>
>
> We've isolated that it happens in
> ServiceInvokerInterceptor.handleMessage(Message)
>
>
>
> Anyone ever see this happen before?
>
>
>
> -Nicholas
>
>
>