You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Dan Checkoway (JIRA)" <ji...@apache.org> on 2009/11/09 15:24:52 UTC

[jira] Created: (CAMEL-2152) Workaround for UnsupportedEncodingException

Workaround for UnsupportedEncodingException
-------------------------------------------

                 Key: CAMEL-2152
                 URL: https://issues.apache.org/activemq/browse/CAMEL-2152
             Project: Apache Camel
          Issue Type: Improvement
          Components: camel-mail
    Affects Versions: 2.0.0
            Reporter: Dan Checkoway
             Fix For: 2.1.0
         Attachments: dcheckoway-charset-fix.diff

Reference this discussion: http://old.nabble.com/Camel-Mail-issue-with-unsupported-charset-td24755585.html

Camel-mail fails to process a message with an unsupported charset in the Content-Type.  It throws an exception and can never get past that message...subsequent messages in the inbox never get processed.

Claus and I came up with a fix, where we make a copy of the MimeMessage object and modify the Content-Type header, stripping the unrecognized charset.

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

[jira] Assigned: (CAMEL-2152) Workaround for UnsupportedEncodingException

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen reassigned CAMEL-2152:
----------------------------------

    Assignee: Claus Ibsen

> Workaround for UnsupportedEncodingException
> -------------------------------------------
>
>                 Key: CAMEL-2152
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2152
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-mail
>    Affects Versions: 2.0.0
>            Reporter: Dan Checkoway
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
>
>         Attachments: dcheckoway-charset-fix.diff
>
>
> Reference this discussion: http://old.nabble.com/Camel-Mail-issue-with-unsupported-charset-td24755585.html
> Camel-mail fails to process a message with an unsupported charset in the Content-Type.  It throws an exception and can never get past that message...subsequent messages in the inbox never get processed.
> Claus and I came up with a fix, where we make a copy of the MimeMessage object and modify the Content-Type header, stripping the unrecognized charset.

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

[jira] Updated: (CAMEL-2152) Workaround for UnsupportedEncodingException

Posted by "Dan Checkoway (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Checkoway updated CAMEL-2152:
---------------------------------

    Attachment: dcheckoway-charset-fix.diff

Patch is now attached.

> Workaround for UnsupportedEncodingException
> -------------------------------------------
>
>                 Key: CAMEL-2152
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2152
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-mail
>    Affects Versions: 2.0.0
>            Reporter: Dan Checkoway
>             Fix For: 2.1.0
>
>         Attachments: dcheckoway-charset-fix.diff
>
>
> Reference this discussion: http://old.nabble.com/Camel-Mail-issue-with-unsupported-charset-td24755585.html
> Camel-mail fails to process a message with an unsupported charset in the Content-Type.  It throws an exception and can never get past that message...subsequent messages in the inbox never get processed.
> Claus and I came up with a fix, where we make a copy of the MimeMessage object and modify the Content-Type header, stripping the unrecognized charset.

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

[jira] Resolved: (CAMEL-2152) Workaround for UnsupportedEncodingException

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/CAMEL-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-2152.
--------------------------------

    Resolution: Fixed

trunk: 834370.

Dan can you test trunk code on you system?

Thanks for the patch.

> Workaround for UnsupportedEncodingException
> -------------------------------------------
>
>                 Key: CAMEL-2152
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2152
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-mail
>    Affects Versions: 2.0.0
>            Reporter: Dan Checkoway
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
>
>         Attachments: dcheckoway-charset-fix.diff
>
>
> Reference this discussion: http://old.nabble.com/Camel-Mail-issue-with-unsupported-charset-td24755585.html
> Camel-mail fails to process a message with an unsupported charset in the Content-Type.  It throws an exception and can never get past that message...subsequent messages in the inbox never get processed.
> Claus and I came up with a fix, where we make a copy of the MimeMessage object and modify the Content-Type header, stripping the unrecognized charset.

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