what does your sending/client invoking code look like, that is, what format are the parameters in, when they are presented to direct:mycall?
There needs to be a binding from the parameter format in the message body to a BeanInvocation or you need to use some scripting support to 'suck' the method parameters from parts of the message body. Let me see if I can find an example in the tests for this. some starting point documentation is at http://activemq.apache.org/camel/bean-binding.html On 03/03/2008, georgiosgeorgiadis <[EMAIL PROTECTED]> wrote: > > Hello everybody, > > Currently I exprerience the following: > > I have a class which defines a method: > > public class MyClass implements java.io.Serializable{ > > public Object getMyObject(String para1, Object param2, int param3, String > param4){ > ....... > } > > } > > I am able to bind it to the camel context but my router complains if i try > to forward via: > > from("direct:mycall").to("bean:MyClass?method=getMyObject"); > > With methods with only one parameter it does really work, passing everything > to the method. > But When the method has more than one params, it complains with: > > java.lang.IllegalStateException: No method invocation could be created, no > maching method could be found on: [EMAIL PROTECTED] > > Any ideas or suggestions on how can I call this method will be much > appreciated. > > Best Regards > > Georgios > > > -- > View this message in context: > http://www.nabble.com/Routing-to-a-method-of-an-object-with-more-than-one-parameters-tp15806637s22882p15806637.html > Sent from the Camel - Users mailing list archive at Nabble.com. > >
