THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Where beanID can be any string which is used to look up the bean in the Registry
Options
| Div | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
| ||||||||||||||||
| Wiki Markup | ||||||||||||||||
| {div:class=confluenceTableSmall}
|| 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. See [Bean Binding] for more details. From *Camel 2.8* onwards you can specify type qualifiers to pin-point the exact method to use for overloaded methods. From *Camel 2.9* onwards you can specify parameter values directly in the method syntax. See more details at [Bean Binding]. |
| {{cache}} | {{boolean}} | {{false}} | If enabled, Camel 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}} | 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. |
{div} |
You can append query options to the URI in the following format, ?option=value&option=value&...
...