On Tue, Jul 14, 2009 at 10:25 AM, Charles Moulliard<[email protected]> wrote: > Hi, > > Is there any other workaround except renaming the method "updatStatus" to > avoid to have an error : AmbiguousMethodCallException. > > In my example, I would like to allow to have two methods with the same name > but having different input parameters and return type > > Here is the route that I want to use : > > from(file) > .to(beanA) // Create Request > .to(beanB) // parse request > .to(queueA) > > from(queueA) > .to(beanC) // validate request > .to(beanD method="updateStatus") // update Status (input parameter : Body = > Request.class, return type = void) > .to(queueB) > > ... > > from(queueX) > .to(beanX) > .to(beanD method="updateStatus") // update Status (input parameter : Body = > Report.class, Header "requestId" String request ID, return type = void) > > Is it possible ? >
Add @Handle to the method you want Camel to choose. > Regards, > > Charles Moulliard > Senior Enterprise Architect > Apache Camel Committer > > ***************************** > blog : http://cmoulliard.blogspot.com > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
