You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2021/04/16 11:37:31 UTC
[camel-spring-boot] 04/04: CAMEL-16524 - Remove Camel-Crypto-CMS
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-spring-boot.git
commit 0e2eebbeee1baf93b90b30b9b7da8a1792738905
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Fri Apr 16 13:34:30 2021 +0200
CAMEL-16524 - Remove Camel-Crypto-CMS
---
docs/modules/ROOT/pages/crypto-cms-starter.adoc | 33 -------------------------
1 file changed, 33 deletions(-)
diff --git a/docs/modules/ROOT/pages/crypto-cms-starter.adoc b/docs/modules/ROOT/pages/crypto-cms-starter.adoc
deleted file mode 100644
index 7a1b82c..0000000
--- a/docs/modules/ROOT/pages/crypto-cms-starter.adoc
+++ /dev/null
@@ -1,33 +0,0 @@
-// spring-boot-auto-configure options: START
-:page-partial:
-:doctitle: Camel Spring Boot Starter for crypto-cms
-
-== Spring Boot Auto-Configuration
-
-When using crypto-cms with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-crypto-cms-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 5 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.crypto-cms.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.crypto-cms.enabled* | Whether to enable auto configuration of the crypto-cms component. This is enabled by default. | | Boolean
-| *camel.component.crypto-cms.enveloped-data-decryptor-configuration* | To configure the shared EnvelopedDataDecryptorConfiguration, which determines the uri parameters for the decrypt operation. The option is a org.apache.camel.component.crypto.cms.crypt.EnvelopedDataDecryptorConfiguration type. | | EnvelopedDataDecryptorConfiguration
-| *camel.component.crypto-cms.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 [...]
-| *camel.component.crypto-cms.signed-data-verifier-configuration* | To configure the shared SignedDataVerifierConfiguration, which determines the uri parameters for the verify operation. The option is a org.apache.camel.component.crypto.cms.sig.SignedDataVerifierConfiguration type. | | SignedDataVerifierConfiguration
-|===
-// spring-boot-auto-configure options: END