[
https://issues.apache.org/jira/browse/CAMEL-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434288#comment-15434288
]
ASF GitHub Bot commented on CAMEL-8108:
---------------------------------------
GitHub user YoshikiHigo opened a pull request:
https://github.com/apache/camel/pull/1135
Followup to CAMEL-8108
This commit is a small followup to CAMEL-8108, which was fixed in
78ac444b6fc02d597145e4b1860a578bf6b67ef2.
Yoshiki, Shinpei, Hideaki, and Mei.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/YoshikiHigo/camel fix02
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1135.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1135
----
commit b4b31bf8596a7c2aa37188fcba6463a93de0df63
Author: Yoshiki Higo <[email protected]>
Date: 2016-08-24T06:42:12Z
Followup to CAMEL-8108
----
> Type converters should not check for null values
> ------------------------------------------------
>
> Key: CAMEL-8108
> URL: https://issues.apache.org/jira/browse/CAMEL-8108
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.15.0
>
>
> There is a number of type converters that due to old time behavior, are still
> doing a != null check for the passed in value.
> As Camel always passes in a value, then this check should be removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
