[ 
https://issues.apache.org/jira/browse/CAMEL-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982127#action_12982127
 ] 

Claus Ibsen commented on CAMEL-3311:
------------------------------------

Christian we can keep most of your logic. Is just that adding the 
{{parameterType}} as a 3rd parameter, just adds a log of new methods in many 
different places.

Something that you actually discovered today. Implementing the ( ) parser is 
fairly easy to do already, if you want to keep the logic to solve ambiguity. We 
can also improve it in 2.7.

You can keep some of the code if you like and add a TODO. Just that the public 
API should not have this new method, because if it's there then people will 
start using it, and then its harder to remove in 2.7, when we introduce the 
parenthesis parser.

BTW: its good work and its great that you _dare_ to work on this as its inside 
the camel-core library.

Don't be afraid to try implement / fix other tickets in camel-core. Its great 
that we have more committers getting their hands dirty in the core.

> 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.

Reply via email to