LibraryToggle FramesPrintFeedback
Name Type Default Description
method String null The method name from the bean that will be invoked. If not provided, Camel will try to determine the method itself. In case of ambiguity an exception will be thrown. From Camel 2.8 onwards you can specify type qualifiers to pin-point exact method to use for overloaded methods. From Camel 2.9 onwards you can specify parameter values directly in the method syntax.
cache boolean false If enabled, Fuse Mediation Router will cache the result of the first Registry look-up. Cache can be enabled if the bean in the Registry is defined as a singleton scope.
multiParameterArray boolean false Fuse Mediation Router 1.5: How to treat the parameters which are passed from the message body; if it is true, the In message body should be an array of parameters.

You can append query options to the URI in the following format, ?option=value&option=value&...

Fuse Mediation Router also supports invoking Bean as an Endpoint. In the route below:

<camelContext xmlns="">
    <from uri="direct:start"/>
    <to uri="myBean"/>
    <to uri="mock:results"/>

<bean id="myBean" class="org.apache.camel.spring.bind.ExampleBean"/>

What happens is that when the exchange is routed to the myBean Fuse Mediation Router will use the Bean Binding to invoke the bean. The source for the bean is just a plain POJO:

public class ExampleBean {

    public String sayHello(String name) {
        return "Hello " + name + "!";

Fuse Mediation Router will use Bean Binding to invoke the sayHello method, by converting the Exchange's In body to the String type and storing the output of the method on the Exchange Out body.

Comments powered by Disqus