[
https://issues.apache.org/jira/browse/CAMEL-5172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269263#comment-13269263
]
Babak Vahdat commented on CAMEL-5172:
-------------------------------------
Thanks for your reply but my question was *why*? Why to deprecate them as they
do provide an easy-to-use shorthand writing. I mean instead of
{code}
exchange.getOut().getMandatoryBody();
{code}
We can simply say:
{code}
ExchangeHelper.getMandatoryOutBody()
{code}
So 1 method call chain instead of 2 ==> shorthand writing.
> TypeConverter - Tighten up API to rethrow failed exception during type
> conversion, and introduce new API for try to convert
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-5172
> URL: https://issues.apache.org/jira/browse/CAMEL-5172
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.8.5, 2.9.3, 2.10.0
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
