Kamelet
To call Kamelets
What’s inside
-
Kamelet component, URI syntax:
kamelet:templateId/routeId
Please refer to the above links for usage and configuration details.
Maven coordinates
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-kamelet-starter</artifactId>
</dependency> Spring Boot Auto-Configuration
The starter supports 11 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
camel.component.kamelet.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.kamelet.block | If sending a message to a kamelet endpoint which has no active consumer, then we can tell the producer to block and wait for the consumer to become active. | true | Boolean |
camel.component.kamelet.bridge-error-handler | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean |
camel.component.kamelet.enabled | Whether to enable auto configuration of the kamelet component. This is enabled by default. | Boolean | |
camel.component.kamelet.lazy-start-producer | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | Boolean |
camel.component.kamelet.location | The location(s) of the Kamelets on the file system. Multiple locations can be set separated by comma. | classpath:kamelets | String |
camel.component.kamelet.no-error-handler | Whether kamelets should use error handling or not. By default, the Kamelet uses the same error handler as from the calling route. This means that if the calling route has error handling that performs retries, or routing to a dead letter channel, then the kamelet route will use this also. This can be turned off by setting this option to true. If off then the kamelet route is not using error handling, and any exception thrown will for source kamelets be logged by the consumer, and the sink/action kamelets will fail processing. | false | Boolean |
camel.component.kamelet.route-properties | Set route local parameters. | Properties> | |
camel.component.kamelet.route-template-loader-listener | To plugin a custom listener for when the Kamelet component is loading Kamelets from external resources. The option is a org.apache.camel.spi.RouteTemplateLoaderListener type. | RouteTemplateLoaderListener | |
camel.component.kamelet.template-properties | Set template local parameters. | Properties> | |
camel.component.kamelet.timeout | The timeout value to use if block is enabled. | 30000 | Long |