Camel Spring Boot Starter for file

Spring Boot Auto-Configuration

When using file with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:

<dependency>
  <groupId>org.apache.camel.springboot</groupId>
  <artifactId>camel-file-starter</artifactId>
  <version>x.x.x</version>
  <!-- use the same version as your Camel core version -->
</dependency>

The component supports 11 options, which are listed below.

Name Description Default Type

camel.component.file.basic-property-binding

Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities

false

Boolean

camel.component.file.bridge-error-handler

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. 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.file.cluster.service.acquire-lock-delay

The time to wait before starting to try to acquire lock.

String

camel.component.file.cluster.service.acquire-lock-interval

The time to wait between attempts to try to acquire lock.

String

camel.component.file.cluster.service.attributes

Custom service attributes.

Map

camel.component.file.cluster.service.enabled

Sets if the file cluster service should be enabled or not, default is false.

false

Boolean

camel.component.file.cluster.service.id

Cluster Service ID

String

camel.component.file.cluster.service.order

Service lookup order/priority.

Integer

camel.component.file.cluster.service.root

The root path.

String

camel.component.file.enabled

Whether to enable auto configuration of the file component. This is enabled by default.

Boolean

camel.component.file.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