[
https://issues.apache.org/jira/browse/CAMEL-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982112#action_12982112
]
Claus Ibsen commented on CAMEL-3311:
------------------------------------
Christian
I dont you should have spend time adding that parameterType in all the
expression and where else it was needed. Because it would have been much better
to implement a simple logic for methodName to support the type directly.
{code}
method=doSomething(Customer)
{code}
Then we avoid adding a lot of new methods to RouteBuilder and what else. We do
have plenty of methods already.
I think we should revert all these changes and implement the parenthesis
solution in Camel 2.7.
If we keep parameterType its not a very powerful addition as the parenthesis
solution would be as it can support multiple types
{code}
method=doSomething(Customer,Boolean)
{code}
> 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.
