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

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2018/08/07 08:50:00 UTC

[jira] [Updated] (CAMEL-12590) Type converter confusion when camel-cxf and camel-mail are in same classpath

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

Claus Ibsen updated CAMEL-12590:
--------------------------------
    Fix Version/s: 2.23.0

> Type converter confusion when camel-cxf and camel-mail are in same classpath
> ----------------------------------------------------------------------------
>
>                 Key: CAMEL-12590
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12590
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cxf, camel-mail
>    Affects Versions: 2.18.5
>            Reporter: Allen Bagwell
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.23.0
>
>
> The CxfRsProducer needs to find a converter to take the String body of an exchange message and turn it into an Object[]. However when camel-mail is present in the classpath the converter search method picks: 
>  
>  com.sun.mail.imap.SortTerm[] org.apache.camel.component.mail.MailConverters.toSortTerm(String msg) 
>  
> This causes the CxfRsProducer to bomb on a NoSuchMethodException. 
>  
>  If camel-mail is removed, the CxfRsProducer client works, finding the right String -> Object[] converter.
> [Issue discussed here on Camel user mailing list|http://camel.465427.n5.nabble.com/Type-converter-misbehavior-with-camel-cxf-and-camel-mail-td5820546.html]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)