camel-validator-kafka-connector sink configuration

Connector Description: Validate the payload using XML Schema and JAXP Validation.

When using camel-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-validator-kafka-connector</artifactId>
  <version>x.x.x</version>
  <!-- use the same version as your Camel Kafka connector version -->
</dependency>

To use this sink connector in Kafka connect you’ll need to set the following connector.class

connector.class=org.apache.camel.kafkaconnector.validator.CamelValidatorSinkConnector

The camel-validator sink connector supports 14 options, which are listed below.

Name Description Default Priority

camel.sink.path.resourceUri

Required URL to a local resource on the classpath, or a reference to lookup a bean in the Registry, or a full URL to a remote resource or resource on the file system which contains the XSD to validate against.

HIGH

camel.sink.endpoint.failOnNullBody

Whether to fail if no body exists.

true

MEDIUM

camel.sink.endpoint.failOnNullHeader

Whether to fail if no header exists when validating against a header.

true

MEDIUM

camel.sink.endpoint.headerName

To validate against a header instead of the message body.

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.errorHandler

To use a custom org.apache.camel.processor.validation.ValidatorErrorHandler. The default error handler captures the errors and throws an exception.

MEDIUM

camel.sink.endpoint.resourceResolver

To use a custom LSResourceResolver. Do not use together with resourceResolverFactory.

MEDIUM

camel.sink.endpoint.resourceResolverFactory

To use a custom LSResourceResolver which depends on a dynamic endpoint resource URI. The default resource resolver factory resturns a resource resolver which can read files from the class path and file system. Do not use together with resourceResolver.

MEDIUM

camel.sink.endpoint.schemaFactory

To use a custom javax.xml.validation.SchemaFactory.

MEDIUM

camel.sink.endpoint.schemaLanguage

Configures the W3C XML Schema Namespace URI.

"http://www.w3.org/2001/XMLSchema"

MEDIUM

camel.sink.endpoint.useSharedSchema

Whether the Schema instance should be shared or not. This option is introduced to work around a JDK 1.6.x bug. Xerces should not have this issue.

true

MEDIUM

camel.component.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.validator.autowiredEnabled

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

MEDIUM

camel.component.validator.resourceResolverFactory

To use a custom LSResourceResolver which depends on a dynamic endpoint resource URI.

MEDIUM

The camel-validator sink connector has no converters out of the box.

The camel-validator sink connector has no transforms out of the box.

The camel-validator sink connector has no aggregation strategies out of the box.

Back to top