[
https://issues.apache.org/jira/browse/CAMEL-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982248#action_12982248
]
Christian Müller commented on CAMEL-3311:
-----------------------------------------
I reverted the changes by applying the following diffs:
svn diff -r 1059343:1059327 > diff_1059343_1059327.txt
svn diff -r 1056749:1056745 > diff_1056749_1056745.txt
and merged the conflicts by hand.
I didn't reverted the String to Class Converter and its unit tests.
I will implement this feature in a better solution in Camel 2.7 with
[CAMEL-3515|https://issues.apache.org/jira/browse/CAMEL-3515].
> bean parameter binding - Add support for type option to force Camel to pick
> method with compatible type
> -------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-3311
> URL: https://issues.apache.org/jira/browse/CAMEL-3311
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.5.0
> Reporter: Claus Ibsen
> Assignee: Christian Müller
> Priority: Minor
> Fix For: 2.6.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Ambiguous-method-invocations-in-bean-binding-tp3248536p3248536.html
> We should introduce a type option so you for example can set it to
> {{java.io.InputStream}} to force Camel to pick a method which this type in
> the method signature.
> This can reduce problems with ambiguous methods, when people haver overloaded
> methods.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
