Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 59. Class Component
Available as of Camel version 2.4
The class: component binds beans to Camel 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.
59.1. URI format Link kopierenLink in die Zwischenablage kopiert!
class:className[?options]
class:className[?options]
Where className is the fully qualified class name to create and use as bean.
59.2. Options Link kopierenLink in die Zwischenablage kopiert!
The Class component has no options.
The Class endpoint is configured using URI syntax:
class:beanName
class:beanName
with the following path and query parameters:
59.2.1. Path Parameters (1 parameters): Link kopierenLink in die Zwischenablage kopiert!
Name | Description | Default | Type |
---|---|---|---|
beanName | Required Sets the name of the bean to invoke | String |
59.2.2. Query Parameters (5 parameters): Link kopierenLink in die Zwischenablage kopiert!
Name | Description | Default | Type |
---|---|---|---|
method (producer) | Sets the name of the method to invoke on the bean | String | |
cache (advanced) | 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. | false | boolean |
multiParameterArray (advanced) | Deprecated How to treat the parameters which are passed from the message body; if it is true, the message body should be an array of parameters. Note: This option is used internally by Camel, and is not intended for end users to use. Deprecation note: This option is used internally by Camel, and is not intended for end users to use. | false | boolean |
parameters (advanced) | Used for configuring additional properties on the bean | Map | |
synchronous (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean |
59.3. Using Link kopierenLink in die Zwischenablage kopiert!
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:
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean").to("mock:result");
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean").to("mock:result");
You can also specify which method to invoke on the MyFooBean
, for example hello
:
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean?method=hello").to("mock:result");
from("direct:start").to("class:org.apache.camel.component.bean.MyFooBean?method=hello").to("mock:result");
59.4. Setting properties on the created instance Link kopierenLink in die Zwischenablage kopiert!
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 details at the Bean component as the class component works in much the same way.
59.5. See Also Link kopierenLink in die Zwischenablage kopiert!
- Configuring Camel
- Component
- Endpoint
- Getting Started
- Bean
- Bean Binding
- Bean Integration