camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Resolved: (CAMEL-2071) Camel Bean component should support methodName and arguments
Date Mon, 19 Oct 2009 06:39:52 GMT


Claus Ibsen resolved CAMEL-2071.

       Resolution: Fixed
    Fix Version/s: 2.1.0

trunk: 826591.

Now Camel is better at picking methods.

Specifying parameters is not implemented as its not the right solution. What should happen
if you specify parameters Camel cannot map, and whatnot.

> Camel Bean component should support methodName and arguments
> ------------------------------------------------------------
>                 Key: CAMEL-2071
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Yuri Schimke
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
> 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.

View raw message