LibraryToggle FramesPrintFeedback

The class: component binds beans to message exchanges. It works in the same way as the Bean component but instead of looking up beans from a Registry it creates the bean based on the class name.

Name Type Default Description
method String null The method name that bean will be invoked. If not provided, Apache Camel will try to pick the method itself. In case of ambiguity an exception is thrown. See Bean Binding for more details.
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.

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

You simply use the class component just as the Bean component but by specifying the fully qualified classname instead. For example to use the MyFooBean you have to do as follows:


You can also specify which method to invoke on the MyFooBean, for example hello:


In the endpoint uri you can specify properties to set on the created instance, for example if it has a setPrefix method:


And you can also use the # syntax to refer to properties to be looked up in the Registry.


Which will lookup a bean from the Registry with the id foo and invoke the setCool method on the created instance of the MyPrefixBean class.

[Tip]See more

See more details at the Bean component as the class component works in much the same way.

Comments powered by Disqus