camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-2071) Camel Bean component should support methodName and arguments
Date Sun, 18 Oct 2009 13:29:52 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54805#action_54805
] 

Claus Ibsen commented on CAMEL-2071:
------------------------------------

I am looking into this about the overloaded method and picking the one with the best matched
type.

> Camel Bean component should support methodName and arguments
> ------------------------------------------------------------
>
>                 Key: CAMEL-2071
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2071
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Yuri Schimke
>            Assignee: Claus Ibsen
>
> When using the Bean component methodName stops working if you have overloaded methods
with that name.  However in the case where the argument type of one of the overloaded forms
matches the body, then this should be used in preference to a method with a different name
but same argument type.
> Currently the following error is thrown
>             <to uri="bean:myBean?method=createInstructions" />
> 	
> org.apache.camel.component.bean.AmbiguousMethodCallException: Ambiguous method invocations
possible: [public final void $Proxy47.someOtherMethod(XXX), public final InstructionSet $Proxy47.createInstructions(XXX)]
on the exchange: Exchange[Message: XXX]	
> 	
> interface MyBean {
> public void someOtherMethod(XXX x);
> public InstructionSet  createInstructions(XXX x);
> public InstructionSet  createInstructions(YYY y);
> }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message