[
https://issues.apache.org/jira/browse/CAMEL-3311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982113#action_12982113
]
Claus Ibsen commented on CAMEL-3311:
------------------------------------
We can also support using wildcards, reg exp, or a ends with check in the type
name. So if you have a domain object with the FQN
{{com.mycompany.myproject.foo.bar.Customer}}, then it would be a tedious to
have to type that, instead you can do
{code}
method=doSomething(*Customer)
{code}
Using a * for wildcard. We could even just default that, so people dont have to
type FQN. Which they still can do if needed.
> 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.
