[ 
https://issues.apache.org/activemq/browse/SMXCOMP-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58902#action_58902
 ] 

Raul Kripalani edited comment on SMXCOMP-289 at 4/16/10 9:37 PM:
-----------------------------------------------------------------

Migrating from Servicemix 3.2.1 to 3.3.1, we found that the resolution for this 
issue broke our JMS service units.

The encoding behaviour was suddenly changed.

What difference does it make if the chosen encoding is the system encoding or 
the SourceTransformer's default encoding (which is obtained from the 
org.apache.servicemix.default.charset property)? I believe that encoding should 
be managed on a per-jms-endpoint basis. Currently it can only be changed at 
system-level, or at ESB-level (SourceTransformer).
  

      was (Author: raulvk):
    Migrating from Servicemix 3.2.1 to 3.3.1, we found that the resolution for 
this issue broke our JMS service units.

The encoding behaviour was suddenly changed.

What difference does it make if the chosen encoding is the system encoding or 
the SourceTransformer's default encoding (which is obtained from the 
org.apache.servicemix.default.charset property)? I believe that encoding should 
be managed on a per-jms-endpoint basis. Currently it can be changed at 
system-level, or at ESB-level (SourceTransformer).
  
  
> Encoding problem ... creating JMS TextMessage from SoapMessage
> --------------------------------------------------------------
>
>                 Key: SMXCOMP-289
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-289
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-jms
>    Affects Versions: 3.2.1
>            Reporter: Michael Halmich
>            Assignee: Guillaume Nodet
>             Fix For: servicemix-jms-2008.01
>
>         Attachments: DefaultJmsMarshalerTest.java, SM-1362.patch, soap.xml
>
>
> In DefaultJmsMarshaler.toJMS(SoapMessage, Session) a TextMessage is created 
> and it's text is set with the return value of 
> ByteArrayOutputStream.toString() ... which uses the platform's default 
> character encoding (in my case Cp1252) ... this destroys german umlauts.
> When used with the right encoding (for example 
> ByteArrayOutputStream.toString(SourceTransformer.getDefaultCharset())) it 
> works.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to