[
https://issues.apache.org/activemq/browse/CAMEL-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1742.
--------------------------------
Resolution: Fixed
1.x: 787571.
> MessageSupport - when using message fallback type converter Camel should not
> report type converter issue with message instead of the real type
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-1742
> URL: https://issues.apache.org/activemq/browse/CAMEL-1742
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 1.6.1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 1.6.2
>
>
> See this forum
> http://fusesource.com/forums/thread.jspa?threadID=963&tstart=0
> {code}
> org.apache.camel.NoTypeConversionAvailableException: No type converter
> available to convert from type: class org.apache.camel.impl.DefaultMessage to
> the required type: java.io.InputStream with value Message:
> org.apache.camel.CamelException: java.lang.Exception
> at
> org.apache.camel.impl.converter.DefaultTypeConverter.doConvertTo(DefaultTypeConverter.java:147)
> at
> org.apache.camel.impl.converter.DefaultTypeConverter.convertTo(DefaultTypeConverter.java:90)
> at
> org.apache.camel.impl.converter.DefaultTypeConverter.convertTo(DefaultTypeConverter.java:86)
> at
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:85)
> at
> org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:52)
> {code}
> Camel should instead this confusing type converter issue, instead it should
> report the real body type as not having a type converter.
> And the fallback should also be optimized like the regular type to only be
> invoked when needed (i.e. to skip when we know for a fact there is no type
> converter possible)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
