[CAMEL-5172] TypeConverter - Tighten up API to rethrow failed exception during type conversion, and introduce new API for try to convert

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.5, 2.9.3, 2.10.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 14/Apr/12 13:51
• Updated: 10/May/12 22:13
• Resolved: 15/Apr/12 15:07

Description

The org.apache.camel.TypeConverter API would not propagate exceptions that would occur during type conversion back to the caller. But instead return null.

We should tighten this up and introduce a new API for trying to convert, so what we would have is

• convertTo = converts, and throws exception if failure during conversion, can return null, if no value to convert, or no type converter exists to do this
• mandatoryConvertTo = convertTo + will throw exception if no value, eg it never returns null
• new tryConvertTo = convertTo but will catch exceptions and return null (like the old behavior)

This introduces an API change in TypeConverter. But it is more intuitive. There is some internal logic that needs to be adjust a bit due they rely on the old behavior.

Issue Links

• is depended upon by: CAMEL-5164 Camel error handler stop routing on original route when an exception occur in the splitter using jaxb marshalled objects