camel-bean-validator-kafka-connector sink configuration
When using camel-bean-validator-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
<dependency>
<groupId>org.apache.camel.kafkaconnector</groupId>
<artifactId>camel-bean-validator-kafka-connector</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel Kafka connector version -->
</dependency>The camel-bean-validator sink connector supports 19 options, which are listed below.
| Name | Description | Default | Priority |
|---|---|---|---|
camel.sink.path.label |
Where label is an arbitrary text value describing the endpoint |
null |
HIGH |
camel.sink.endpoint.group |
To use a custom validation group |
"javax.validation.groups.Default" |
MEDIUM |
camel.sink.endpoint.ignoreXmlConfiguration |
Whether to ignore data from the META-INF/validation.xml file. |
false |
MEDIUM |
camel.sink.endpoint.lazyStartProducer |
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 |
MEDIUM |
camel.sink.endpoint.basicPropertyBinding |
Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
MEDIUM |
camel.sink.endpoint.constraintValidatorFactory |
To use a custom ConstraintValidatorFactory |
null |
MEDIUM |
camel.sink.endpoint.messageInterpolator |
To use a custom MessageInterpolator |
null |
MEDIUM |
camel.sink.endpoint.synchronous |
Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). |
false |
MEDIUM |
camel.sink.endpoint.traversableResolver |
To use a custom TraversableResolver |
null |
MEDIUM |
camel.sink.endpoint.validationProviderResolver |
To use a a custom ValidationProviderResolver |
null |
MEDIUM |
camel.sink.endpoint.validatorFactory |
To use a custom ValidatorFactory |
null |
MEDIUM |
camel.component.bean-validator.ignoreXml Configuration |
Whether to ignore data from the META-INF/validation.xml file. |
false |
MEDIUM |
camel.component.bean-validator.lazyStartProducer |
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 |
MEDIUM |
camel.component.bean-validator.basicProperty Binding |
Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
MEDIUM |
camel.component.bean-validator.constraintValidator Factory |
To use a custom ConstraintValidatorFactory |
null |
MEDIUM |
camel.component.bean-validator.messageInterpolator |
To use a custom MessageInterpolator |
null |
MEDIUM |
camel.component.bean-validator.traversableResolver |
To use a custom TraversableResolver |
null |
MEDIUM |
camel.component.bean-validator.validationProvider Resolver |
To use a a custom ValidationProviderResolver |
null |
MEDIUM |
camel.component.bean-validator.validatorFactory |
To use a custom ValidatorFactory |
null |
MEDIUM |