THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Where someName can be any string which is used to lookup the bean in the Registry
Options
Name | Type | Default | Description Example | ||||||
|---|---|---|---|---|---|---|---|---|---|
method | Required? | default value | String | null method | The method name that bean will be inovked | method=someMethod | No | someMethod defines the name of the method to invoke,This will use the Bean Binding to map the message exchange to the bean. | invoked. If not provided Camel will try to pick the method itself. In case of ambiguity an exception is thrown. See Bean Binding for more details. |
cache | boolean | false | If enabled Camel will cache the result of the first Registry lookup. Cache can be enabled if the bean in the Registry is defined as a singleton scope. | ||||||
multiParameterArray | boolean | false | multiParameterArray | New option in Camel 1.5: How to treat the parameters which are passed from the message body, if it is true, the in message body should be the an array of parameters | multiParameterArray=true | No | false . |
Using
The object instance that is used to consume messages must be explicitly registered with the Registry. For example if you are using Spring you must define the bean in the spring.xml; or if you don't use Spring then put the bean in JNDI.
...