You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2010/06/28 12:36:51 UTC

[jira] Created: (CAMEL-2870) camel-mail using the exchange charset name property as a fall back of the charset which used in content-type

camel-mail using the exchange charset name property as a fall back of the charset which used in content-type 
-------------------------------------------------------------------------------------------------------------

                 Key: CAMEL-2870
                 URL: https://issues.apache.org/activemq/browse/CAMEL-2870
             Project: Apache Camel
          Issue Type: Improvement
          Components: camel-mail
            Reporter: Willem Jiang
            Assignee: Willem Jiang
             Fix For: 2.4.0


In this way, we don't need to specify the content-type header if we already specify the charsetname in the exchange property.


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

[jira] Resolved: (CAMEL-2870) camel-mail using the exchange charset name property as a fall back of the charset which used in content-type

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.

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

Willem Jiang resolved CAMEL-2870.
---------------------------------

    Resolution: Fixed

> camel-mail using the exchange charset name property as a fall back of the charset which used in content-type 
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2870
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2870
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-mail
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.4.0
>
>
> In this way, we don't need to specify the content-type header if we already specify the charsetname in the exchange property.

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