[camel-kafka-connector] 03/03: Removed docs for bean-validator

[ac...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch bean-val-removed
in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git

commit b14a718719ba5f341b913537246b46d1279400d6
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Thu Sep 24 15:01:47 2020 +0200

    Removed docs for bean-validator
---
 .../camel-bean-validator-kafka-sink-connector.adoc | 68 ----------------------
 1 file changed, 68 deletions(-)

diff --git a/docs/modules/ROOT/pages/connectors/camel-bean-validator-kafka-sink-connector.adoc b/docs/modules/ROOT/pages/connectors/camel-bean-validator-kafka-sink-connector.adoc
deleted file mode 100644
index 2c61336..0000000
--- a/docs/modules/ROOT/pages/connectors/camel-bean-validator-kafka-sink-connector.adoc
+++ /dev/null
@@ -1,68 +0,0 @@
-// kafka-connector options: START
-[[camel-bean-validator-kafka-connector-sink]]
-= 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:
-
-[source,xml]
-----
-<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>
-----
-
-To use this Sink connector in Kafka connect you'll need to set the following connector.class
-
-[source,java]
-----
-connector.class=org.apache.camel.kafkaconnector.beanvalidator.CamelBeanvalidatorSinkConnector
-----
-
-
-The camel-bean-validator sink connector supports 19 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| 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 cre [...]
-| *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 process [...]
-| *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
-|===
-
-
-
-The camel-bean-validator sink connector has no converters out of the box.
-
-
-
-
-
-The camel-bean-validator sink connector has no transforms out of the box.
-
-
-
-
-
-The camel-bean-validator sink connector has no aggregation strategies out of the box.
-// kafka-connector options: END