This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-spring-boot.git
The following commit(s) were added to refs/heads/master by this push:
new 2189cae Regen
2189cae is described below
commit 2189caeb3b40d94bd984c384338e08d364d12f64
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Wed May 6 10:05:03 2020 +0200
Regen
---
.../camel/springboot/catalog/components/chunk.json | 2 ++
.../springboot/catalog/components/freemarker.json | 1 +
.../camel/springboot/catalog/components/jolt.json | 2 ++
.../camel/springboot/catalog/components/jslt.json | 2 ++
.../springboot/catalog/components/mustache.json | 2 ++
.../camel/springboot/catalog/components/mvel.json | 2 ++
.../catalog/components/robotframework.json | 2 ++
.../catalog/components/string-template.json | 2 ++
.../springboot/catalog/components/velocity.json | 2 ++
.../catalog/others/undertow-spring-security.json | 15 ++++++++++
components-starter/README.adoc | 5 +++-
.../src/main/docs/chunk-starter.adoc | 4 +--
.../springboot/ChunkComponentConfiguration.java | 15 ++++++++++
.../src/main/docs/jolt-starter.adoc | 4 +--
.../springboot/JoltComponentConfiguration.java | 15 ++++++++++
.../src/main/docs/jslt-starter.adoc | 4 +--
.../springboot/JsltComponentConfiguration.java | 15 ++++++++++
.../src/main/docs/mustache-starter.adoc | 4 +--
.../springboot/MustacheComponentConfiguration.java | 15 ++++++++++
.../src/main/docs/mvel-starter.adoc | 4 +--
.../springboot/MvelComponentConfiguration.java | 15 ++++++++++
.../src/main/docs/robotframework-starter.adoc | 3 +-
.../RobotFrameworkComponentConfiguration.java | 15 ++++++++++
.../src/main/docs/stringtemplate-starter.adoc | 4 +--
.../StringTemplateComponentConfiguration.java | 15 ++++++++++
.../src/main/docs/velocity-starter.adoc | 4 +--
.../springboot/VelocityComponentConfiguration.java | 15 ++++++++++
components-starter/pom.xml | 1 +
docs/modules/ROOT/pages/chunk-starter.adoc | 4 +--
docs/modules/ROOT/pages/jolt-starter.adoc | 4 +--
docs/modules/ROOT/pages/jslt-starter.adoc | 4 +--
docs/modules/ROOT/pages/list.adoc | 5 +++-
docs/modules/ROOT/pages/mustache-starter.adoc | 4 +--
docs/modules/ROOT/pages/mvel-starter.adoc | 4 +--
.../modules/ROOT/pages/robotframework-starter.adoc | 3 +-
.../modules/ROOT/pages/stringtemplate-starter.adoc | 4 +--
.../pages/undertow-spring-security-starter.adoc | 33 ++++++++++++++++++++++
docs/modules/ROOT/pages/velocity-starter.adoc | 4 +--
tooling/camel-spring-boot-dependencies/pom.xml | 10 -------
39 files changed, 226 insertions(+), 42 deletions(-)
diff --git
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/chunk.json
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/chunk.json
index 24a23f4..fe060ec 100644
---
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/chunk.json
+++
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/chunk.json
@@ -21,11 +21,13 @@
"lenientProperties": false
},
"componentProperties": {
+ "allowTemplateFromHeader": { "kind": "property", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the he [...]
"lazyStartProducer": { "kind": "property", "displayName": "Lazy Start
Producer", "group": "producer", "label": "producer", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "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 r [...]
"basicPropertyBinding": { "kind": "property", "displayName": "Basic
Property Binding", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities" }
},
"properties": {
"resourceUri": { "kind": "path", "displayName": "Resource Uri", "group":
"producer", "label": "", "required": true, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "deprecationNote": "", "secret":
false, "description": "Path to the resource. You can prefix with: classpath,
file, http, ref, or bean. classpath, file and http loads the resource using
these protocols (classpath is default). ref will lookup the resource in the
registry. bean will call a method on a [...]
+ "allowTemplateFromHeader": { "kind": "parameter", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the h [...]
"contentCache": { "kind": "parameter", "displayName": "Content Cache",
"group": "producer", "label": "", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
"false", "description": "Sets whether to use resource content cache or not" },
"encoding": { "kind": "parameter", "displayName": "Encoding", "group":
"producer", "label": "", "required": false, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "secret": false, "description":
"Define the encoding of the body" },
"extension": { "kind": "parameter", "displayName": "Extension", "group":
"producer", "label": "", "required": false, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "secret": false, "description":
"Define the file extension of the template" },
diff --git
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/freemarker.json
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/freemarker.json
index 08fdcee..aa26994 100644
---
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/freemarker.json
+++
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/freemarker.json
@@ -28,6 +28,7 @@
},
"properties": {
"resourceUri": { "kind": "path", "displayName": "Resource Uri", "group":
"producer", "label": "", "required": true, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "deprecationNote": "", "secret":
false, "description": "Path to the resource. You can prefix with: classpath,
file, http, ref, or bean. classpath, file and http loads the resource using
these protocols (classpath is default). ref will lookup the resource in the
registry. bean will call a method on a [...]
+ "allowTemplateFromHeader": { "kind": "parameter", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the h [...]
"configuration": { "kind": "parameter", "displayName": "Configuration",
"group": "producer", "label": "", "required": false, "type": "object",
"javaType": "freemarker.template.Configuration", "deprecated": false, "secret":
false, "description": "Sets the Freemarker configuration to use" },
"contentCache": { "kind": "parameter", "displayName": "Content Cache",
"group": "producer", "label": "", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
"false", "description": "Sets whether to use resource content cache or not" },
"encoding": { "kind": "parameter", "displayName": "Encoding", "group":
"producer", "label": "", "required": false, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "secret": false, "description": "Sets
the encoding to be used for loading the template file." },
diff --git
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/jolt.json
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/jolt.json
index e6cc8ee..7b0606d 100644
---
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/jolt.json
+++
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/jolt.json
@@ -21,12 +21,14 @@
"lenientProperties": false
},
"componentProperties": {
+ "allowTemplateFromHeader": { "kind": "property", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the he [...]
"lazyStartProducer": { "kind": "property", "displayName": "Lazy Start
Producer", "group": "producer", "label": "producer", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "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 r [...]
"basicPropertyBinding": { "kind": "property", "displayName": "Basic
Property Binding", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities" },
"transform": { "kind": "property", "displayName": "Transform", "group":
"advanced", "label": "advanced", "required": false, "type": "object",
"javaType": "com.bazaarvoice.jolt.Transform", "deprecated": false, "secret":
false, "description": "Explicitly sets the Transform to use. If not set a
Transform specified by the transformDsl will be created" }
},
"properties": {
"resourceUri": { "kind": "path", "displayName": "Resource Uri", "group":
"producer", "label": "", "required": true, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "deprecationNote": "", "secret":
false, "description": "Path to the resource. You can prefix with: classpath,
file, http, ref, or bean. classpath, file and http loads the resource using
these protocols (classpath is default). ref will lookup the resource in the
registry. bean will call a method on a [...]
+ "allowTemplateFromHeader": { "kind": "parameter", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the h [...]
"contentCache": { "kind": "parameter", "displayName": "Content Cache",
"group": "producer", "label": "", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
"false", "description": "Sets whether to use resource content cache or not" },
"inputType": { "kind": "parameter", "displayName": "Input Type", "group":
"producer", "label": "", "required": false, "type": "object", "javaType":
"org.apache.camel.component.jolt.JoltInputOutputType", "enum": [ "Hydrated",
"JsonString" ], "deprecated": false, "secret": false, "defaultValue":
"Hydrated", "description": "Specifies if the input is hydrated JSON or a JSON
String." },
"lazyStartProducer": { "kind": "parameter", "displayName": "Lazy Start
Producer", "group": "producer", "label": "producer", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "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 [...]
diff --git
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/jslt.json
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/jslt.json
index a8bbc77..e4049db 100644
---
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/jslt.json
+++
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/jslt.json
@@ -21,12 +21,14 @@
"lenientProperties": false
},
"componentProperties": {
+ "allowTemplateFromHeader": { "kind": "property", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the he [...]
"lazyStartProducer": { "kind": "property", "displayName": "Lazy Start
Producer", "group": "producer", "label": "producer", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "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 r [...]
"basicPropertyBinding": { "kind": "property", "displayName": "Basic
Property Binding", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities" },
"functions": { "kind": "property", "displayName": "Functions", "group":
"advanced", "label": "advanced", "required": false, "type": "array",
"javaType": "java.util.Collection<com.schibsted.spt.data.jslt.Function>",
"deprecated": false, "secret": false, "description": "JSLT can be extended by
plugging in functions written in Java." }
},
"properties": {
"resourceUri": { "kind": "path", "displayName": "Resource Uri", "group":
"producer", "label": "", "required": true, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "deprecationNote": "", "secret":
false, "description": "Path to the resource. You can prefix with: classpath,
file, http, ref, or bean. classpath, file and http loads the resource using
these protocols (classpath is default). ref will lookup the resource in the
registry. bean will call a method on a [...]
+ "allowTemplateFromHeader": { "kind": "parameter", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the h [...]
"contentCache": { "kind": "parameter", "displayName": "Content Cache",
"group": "producer", "label": "", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
"false", "description": "Sets whether to use resource content cache or not" },
"prettyPrint": { "kind": "parameter", "displayName": "Pretty Print",
"group": "common", "label": "common", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
"false", "description": "If true, JSON in output message is pretty printed." },
"lazyStartProducer": { "kind": "parameter", "displayName": "Lazy Start
Producer", "group": "producer", "label": "producer", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "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 [...]
diff --git
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/mustache.json
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/mustache.json
index 492976b..d0252d2 100644
---
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/mustache.json
+++
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/mustache.json
@@ -21,12 +21,14 @@
"lenientProperties": false
},
"componentProperties": {
+ "allowTemplateFromHeader": { "kind": "property", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the he [...]
"lazyStartProducer": { "kind": "property", "displayName": "Lazy Start
Producer", "group": "producer", "label": "producer", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "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 r [...]
"basicPropertyBinding": { "kind": "property", "displayName": "Basic
Property Binding", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities" },
"mustacheFactory": { "kind": "property", "displayName": "Mustache
Factory", "group": "advanced", "label": "advanced", "required": false, "type":
"object", "javaType": "com.github.mustachejava.MustacheFactory", "deprecated":
false, "secret": false, "description": "To use a custom MustacheFactory" }
},
"properties": {
"resourceUri": { "kind": "path", "displayName": "Resource Uri", "group":
"producer", "label": "", "required": true, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "deprecationNote": "", "secret":
false, "description": "Path to the resource. You can prefix with: classpath,
file, http, ref, or bean. classpath, file and http loads the resource using
these protocols (classpath is default). ref will lookup the resource in the
registry. bean will call a method on a [...]
+ "allowTemplateFromHeader": { "kind": "parameter", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the h [...]
"contentCache": { "kind": "parameter", "displayName": "Content Cache",
"group": "producer", "label": "", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
"false", "description": "Sets whether to use resource content cache or not" },
"encoding": { "kind": "parameter", "displayName": "Encoding", "group":
"producer", "label": "", "required": false, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "secret": false, "description":
"Character encoding of the resource content." },
"endDelimiter": { "kind": "parameter", "displayName": "End Delimiter",
"group": "producer", "label": "", "required": false, "type": "string",
"javaType": "java.lang.String", "deprecated": false, "secret": false,
"defaultValue": "}}", "description": "Characters used to mark template code
end." },
diff --git
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/mvel.json
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/mvel.json
index df025e8..6c1ff02 100644
---
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/mvel.json
+++
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/mvel.json
@@ -21,11 +21,13 @@
"lenientProperties": false
},
"componentProperties": {
+ "allowTemplateFromHeader": { "kind": "property", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the he [...]
"lazyStartProducer": { "kind": "property", "displayName": "Lazy Start
Producer", "group": "producer", "label": "producer", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "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 r [...]
"basicPropertyBinding": { "kind": "property", "displayName": "Basic
Property Binding", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities" }
},
"properties": {
"resourceUri": { "kind": "path", "displayName": "Resource Uri", "group":
"producer", "label": "", "required": true, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "deprecationNote": "", "secret":
false, "description": "Path to the resource. You can prefix with: classpath,
file, http, ref, or bean. classpath, file and http loads the resource using
these protocols (classpath is default). ref will lookup the resource in the
registry. bean will call a method on a [...]
+ "allowTemplateFromHeader": { "kind": "parameter", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the h [...]
"contentCache": { "kind": "parameter", "displayName": "Content Cache",
"group": "producer", "label": "", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
"false", "description": "Sets whether to use resource content cache or not" },
"encoding": { "kind": "parameter", "displayName": "Encoding", "group":
"producer", "label": "", "required": false, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "secret": false, "description":
"Character encoding of the resource content." },
"lazyStartProducer": { "kind": "parameter", "displayName": "Lazy Start
Producer", "group": "producer", "label": "producer", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "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 [...]
diff --git
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/robotframework.json
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/robotframework.json
index e746b75..8e87579 100644
---
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/robotframework.json
+++
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/robotframework.json
@@ -21,6 +21,7 @@
"lenientProperties": false
},
"componentProperties": {
+ "allowTemplateFromHeader": { "kind": "property", "displayName": "Allow
Template From Header", "group": "common", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "configurationClass":
"org.apache.camel.component.robotframework.RobotFrameworkCamelConfiguration",
"configurationField": "configuration", "description": "Whether to allow to use
resource template from header or not (default false). Enabl [...]
"argumentFile": { "kind": "property", "displayName": "Argument File",
"group": "common", "label": "", "required": false, "type": "string",
"javaType": "java.io.File", "deprecated": false, "secret": false,
"configurationClass":
"org.apache.camel.component.robotframework.RobotFrameworkCamelConfiguration",
"configurationField": "configuration", "description": "A text file to read more
arguments from." },
"combinedTagStats": { "kind": "property", "displayName": "Combined Tag
Stats", "group": "common", "label": "", "required": false, "type": "string",
"javaType": "java.lang.String", "deprecated": false, "secret": false,
"configurationClass":
"org.apache.camel.component.robotframework.RobotFrameworkCamelConfiguration",
"configurationField": "configuration", "description": "Creates combined
statistics based on tags. Use the format tags:title List" },
"criticalTags": { "kind": "property", "displayName": "Critical Tags",
"group": "common", "label": "", "required": false, "type": "string",
"javaType": "java.lang.String", "deprecated": false, "secret": false,
"configurationClass":
"org.apache.camel.component.robotframework.RobotFrameworkCamelConfiguration",
"configurationField": "configuration", "description": "Tests that have the
given tags are considered critical. List" },
@@ -73,6 +74,7 @@
},
"properties": {
"resourceUri": { "kind": "path", "displayName": "Resource Uri", "group":
"common", "label": "", "required": true, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "deprecationNote": "", "secret":
false, "description": "Path to the resource. You can prefix with: classpath,
file, http, ref, or bean. classpath, file and http loads the resource using
these protocols (classpath is default). ref will lookup the resource in the
registry. bean will call a method on a be [...]
+ "allowTemplateFromHeader": { "kind": "parameter", "displayName": "Allow
Template From Header", "group": "common", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "configurationClass":
"org.apache.camel.component.robotframework.RobotFrameworkCamelConfiguration",
"configurationField": "configuration", "description": "Whether to allow to use
resource template from header or not (default false). Enab [...]
"argumentFile": { "kind": "parameter", "displayName": "Argument File",
"group": "common", "label": "", "required": false, "type": "string",
"javaType": "java.io.File", "deprecated": false, "secret": false,
"configurationClass":
"org.apache.camel.component.robotframework.RobotFrameworkCamelConfiguration",
"configurationField": "configuration", "description": "A text file to read more
arguments from." },
"combinedTagStats": { "kind": "parameter", "displayName": "Combined Tag
Stats", "group": "common", "label": "", "required": false, "type": "string",
"javaType": "java.lang.String", "deprecated": false, "secret": false,
"configurationClass":
"org.apache.camel.component.robotframework.RobotFrameworkCamelConfiguration",
"configurationField": "configuration", "description": "Creates combined
statistics based on tags. Use the format tags:title List" },
"contentCache": { "kind": "parameter", "displayName": "Content Cache",
"group": "common", "label": "", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
"false", "description": "Sets whether to use resource content cache or not" },
diff --git
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/string-template.json
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/string-template.json
index 1d71eb2..3ec1d0c 100644
---
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/string-template.json
+++
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/string-template.json
@@ -21,11 +21,13 @@
"lenientProperties": false
},
"componentProperties": {
+ "allowTemplateFromHeader": { "kind": "property", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the he [...]
"lazyStartProducer": { "kind": "property", "displayName": "Lazy Start
Producer", "group": "producer", "label": "producer", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "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 r [...]
"basicPropertyBinding": { "kind": "property", "displayName": "Basic
Property Binding", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities" }
},
"properties": {
"resourceUri": { "kind": "path", "displayName": "Resource Uri", "group":
"producer", "label": "", "required": true, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "deprecationNote": "", "secret":
false, "description": "Path to the resource. You can prefix with: classpath,
file, http, ref, or bean. classpath, file and http loads the resource using
these protocols (classpath is default). ref will lookup the resource in the
registry. bean will call a method on a [...]
+ "allowTemplateFromHeader": { "kind": "parameter", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the h [...]
"contentCache": { "kind": "parameter", "displayName": "Content Cache",
"group": "producer", "label": "", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
"false", "description": "Sets whether to use resource content cache or not" },
"delimiterStart": { "kind": "parameter", "displayName": "Delimiter Start",
"group": "producer", "label": "", "required": false, "type": "string",
"javaType": "char", "deprecated": false, "secret": false, "defaultValue": "<",
"description": "The variable start delimiter" },
"delimiterStop": { "kind": "parameter", "displayName": "Delimiter Stop",
"group": "producer", "label": "", "required": false, "type": "string",
"javaType": "char", "deprecated": false, "secret": false, "defaultValue": ">",
"description": "The variable end delimiter" },
diff --git
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/velocity.json
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/velocity.json
index 4e9bcbc..8646ad8 100644
---
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/velocity.json
+++
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/components/velocity.json
@@ -21,12 +21,14 @@
"lenientProperties": false
},
"componentProperties": {
+ "allowTemplateFromHeader": { "kind": "property", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the he [...]
"lazyStartProducer": { "kind": "property", "displayName": "Lazy Start
Producer", "group": "producer", "label": "producer", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "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 r [...]
"basicPropertyBinding": { "kind": "property", "displayName": "Basic
Property Binding", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether the component should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities" },
"velocityEngine": { "kind": "property", "displayName": "Velocity Engine",
"group": "advanced", "label": "advanced", "required": false, "type": "object",
"javaType": "org.apache.velocity.app.VelocityEngine", "deprecated": false,
"secret": false, "description": "To use the VelocityEngine otherwise a new
engine is created" }
},
"properties": {
"resourceUri": { "kind": "path", "displayName": "Resource Uri", "group":
"producer", "label": "", "required": true, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "deprecationNote": "", "secret":
false, "description": "Path to the resource. You can prefix with: classpath,
file, http, ref, or bean. classpath, file and http loads the resource using
these protocols (classpath is default). ref will lookup the resource in the
registry. bean will call a method on a [...]
+ "allowTemplateFromHeader": { "kind": "parameter", "displayName": "Allow
Template From Header", "group": "producer", "label": "", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": "false", "description": "Whether to allow to use resource
template from header or not (default false). Enabling this allows to specify
dynamic templates via message header. However this can be seen as a potential
security vulnerability if the h [...]
"contentCache": { "kind": "parameter", "displayName": "Content Cache",
"group": "producer", "label": "", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
"false", "description": "Sets whether to use resource content cache or not" },
"encoding": { "kind": "parameter", "displayName": "Encoding", "group":
"producer", "label": "", "required": false, "type": "string", "javaType":
"java.lang.String", "deprecated": false, "secret": false, "description":
"Character encoding of the resource content." },
"lazyStartProducer": { "kind": "parameter", "displayName": "Lazy Start
Producer", "group": "producer", "label": "producer", "required": false, "type":
"boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "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 [...]
diff --git
a/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/others/undertow-spring-security.json
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/others/undertow-spring-security.json
new file mode 100644
index 0000000..54a059e
--- /dev/null
+++
b/catalog/camel-catalog-provider-springboot/src/main/resources/org/apache/camel/springboot/catalog/others/undertow-spring-security.json
@@ -0,0 +1,15 @@
+{
+ "other": {
+ "kind": "other",
+ "name": "undertow-spring-security",
+ "title": "Undertow Spring Security",
+ "description": "Spring Security Provider for camel-undertow",
+ "deprecated": false,
+ "firstVersion": "3.3.0",
+ "label": "security",
+ "supportLevel": "Preview",
+ "groupId": "org.apache.camel.springboot",
+ "artifactId": "camel-undertow-spring-security-starter",
+ "version": "3.3.0-SNAPSHOT"
+ }
+}
diff --git a/components-starter/README.adoc b/components-starter/README.adoc
index 40e8707..cc2bb05 100644
--- a/components-starter/README.adoc
+++ b/components-starter/README.adoc
@@ -1213,7 +1213,7 @@ Number of Camel languages: 17 in 11 JAR artifacts (0
deprecated)
== Miscellaneous Extensions
// others: START
-Number of miscellaneous extensions: 22 in 22 JAR artifacts (0 deprecated)
+Number of miscellaneous extensions: 23 in 23 JAR artifacts (0 deprecated)
[width="100%",cols="4,1,5",options="header"]
|===
@@ -1282,6 +1282,9 @@ Number of miscellaneous extensions: 22 in 22 JAR
artifacts (0 deprecated)
|
link:https://camel.apache.org/components/latest/others/swagger-java.html[Swagger
Java] +
(camel-swagger-java-starter) | 2.16 | Rest-dsl support for using swagger
api-doc
+|
link:https://camel.apache.org/components/latest/others/undertow-spring-security.html[Undertow
Spring Security] +
+(camel-undertow-spring-security-starter) | 3.3 | Spring Security Provider for
camel-undertow
+
| link:https://camel.apache.org/components/latest/others/zipkin.html[Zipkin] +
(camel-zipkin-starter) | 2.18 | Distributed message tracing using Zipkin
|===
diff --git
a/components-starter/camel-chunk-starter/src/main/docs/chunk-starter.adoc
b/components-starter/camel-chunk-starter/src/main/docs/chunk-starter.adoc
index 9d775c3..69f708d 100644
--- a/components-starter/camel-chunk-starter/src/main/docs/chunk-starter.adoc
+++ b/components-starter/camel-chunk-starter/src/main/docs/chunk-starter.adoc
@@ -17,16 +17,16 @@ When using chunk with Spring Boot make sure to use the
following Maven dependenc
----
-The component supports 3 options, which are listed below.
+The component supports 4 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.chunk.allow-template-from-header* | Whether to allow to use
resource template from header or not (default false). Enabling this allows to
specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.chunk.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.chunk.enabled* | Whether to enable auto configuration of
the chunk component. This is enabled by default. | | Boolean
| *camel.component.chunk.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 [...]
|===
-
// spring-boot-auto-configure options: END
diff --git
a/components-starter/camel-chunk-starter/src/main/java/org/apache/camel/component/chunk/springboot/ChunkComponentConfiguration.java
b/components-starter/camel-chunk-starter/src/main/java/org/apache/camel/component/chunk/springboot/ChunkComponentConfiguration.java
index 4b02aa8..a83506e 100644
---
a/components-starter/camel-chunk-starter/src/main/java/org/apache/camel/component/chunk/springboot/ChunkComponentConfiguration.java
+++
b/components-starter/camel-chunk-starter/src/main/java/org/apache/camel/component/chunk/springboot/ChunkComponentConfiguration.java
@@ -37,6 +37,13 @@ public class ChunkComponentConfiguration
*/
private Boolean enabled;
/**
+ * Whether to allow to use resource template from header or not (default
+ * false). Enabling this allows to specify dynamic templates via message
+ * header. However this can be seen as a potential security vulnerability
if
+ * the header is coming from a malicious user, so use this with care.
+ */
+ private Boolean allowTemplateFromHeader = false;
+ /**
* 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
@@ -53,6 +60,14 @@ public class ChunkComponentConfiguration
*/
private Boolean basicPropertyBinding = false;
+ public Boolean getAllowTemplateFromHeader() {
+ return allowTemplateFromHeader;
+ }
+
+ public void setAllowTemplateFromHeader(Boolean allowTemplateFromHeader) {
+ this.allowTemplateFromHeader = allowTemplateFromHeader;
+ }
+
public Boolean getLazyStartProducer() {
return lazyStartProducer;
}
diff --git
a/components-starter/camel-jolt-starter/src/main/docs/jolt-starter.adoc
b/components-starter/camel-jolt-starter/src/main/docs/jolt-starter.adoc
index ba78cf4..2103a02 100644
--- a/components-starter/camel-jolt-starter/src/main/docs/jolt-starter.adoc
+++ b/components-starter/camel-jolt-starter/src/main/docs/jolt-starter.adoc
@@ -17,17 +17,17 @@ When using jolt with Spring Boot make sure to use the
following Maven dependency
----
-The component supports 4 options, which are listed below.
+The component supports 5 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.jolt.allow-template-from-header* | Whether to allow to use
resource template from header or not (default false). Enabling this allows to
specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.jolt.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.jolt.enabled* | Whether to enable auto configuration of the
jolt component. This is enabled by default. | | Boolean
| *camel.component.jolt.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 [...]
| *camel.component.jolt.transform* | Explicitly sets the Transform to use. If
not set a Transform specified by the transformDsl will be created. The option
is a com.bazaarvoice.jolt.Transform type. | | String
|===
-
// spring-boot-auto-configure options: END
diff --git
a/components-starter/camel-jolt-starter/src/main/java/org/apache/camel/component/jolt/springboot/JoltComponentConfiguration.java
b/components-starter/camel-jolt-starter/src/main/java/org/apache/camel/component/jolt/springboot/JoltComponentConfiguration.java
index ab3db60..30baf63 100644
---
a/components-starter/camel-jolt-starter/src/main/java/org/apache/camel/component/jolt/springboot/JoltComponentConfiguration.java
+++
b/components-starter/camel-jolt-starter/src/main/java/org/apache/camel/component/jolt/springboot/JoltComponentConfiguration.java
@@ -37,6 +37,13 @@ public class JoltComponentConfiguration
*/
private Boolean enabled;
/**
+ * Whether to allow to use resource template from header or not (default
+ * false). Enabling this allows to specify dynamic templates via message
+ * header. However this can be seen as a potential security vulnerability
if
+ * the header is coming from a malicious user, so use this with care.
+ */
+ private Boolean allowTemplateFromHeader = false;
+ /**
* 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
@@ -59,6 +66,14 @@ public class JoltComponentConfiguration
*/
private String transform;
+ public Boolean getAllowTemplateFromHeader() {
+ return allowTemplateFromHeader;
+ }
+
+ public void setAllowTemplateFromHeader(Boolean allowTemplateFromHeader) {
+ this.allowTemplateFromHeader = allowTemplateFromHeader;
+ }
+
public Boolean getLazyStartProducer() {
return lazyStartProducer;
}
diff --git
a/components-starter/camel-jslt-starter/src/main/docs/jslt-starter.adoc
b/components-starter/camel-jslt-starter/src/main/docs/jslt-starter.adoc
index 3fd0119..aef4d34 100644
--- a/components-starter/camel-jslt-starter/src/main/docs/jslt-starter.adoc
+++ b/components-starter/camel-jslt-starter/src/main/docs/jslt-starter.adoc
@@ -17,17 +17,17 @@ When using jslt with Spring Boot make sure to use the
following Maven dependency
----
-The component supports 4 options, which are listed below.
+The component supports 5 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.jslt.allow-template-from-header* | Whether to allow to use
resource template from header or not (default false). Enabling this allows to
specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.jslt.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.jslt.enabled* | Whether to enable auto configuration of the
jslt component. This is enabled by default. | | Boolean
| *camel.component.jslt.functions* | JSLT can be extended by plugging in
functions written in Java. | | Collection
| *camel.component.jslt.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 [...]
|===
-
// spring-boot-auto-configure options: END
diff --git
a/components-starter/camel-jslt-starter/src/main/java/org/apache/camel/component/jslt/springboot/JsltComponentConfiguration.java
b/components-starter/camel-jslt-starter/src/main/java/org/apache/camel/component/jslt/springboot/JsltComponentConfiguration.java
index 7241a7e..bb587cb 100644
---
a/components-starter/camel-jslt-starter/src/main/java/org/apache/camel/component/jslt/springboot/JsltComponentConfiguration.java
+++
b/components-starter/camel-jslt-starter/src/main/java/org/apache/camel/component/jslt/springboot/JsltComponentConfiguration.java
@@ -39,6 +39,13 @@ public class JsltComponentConfiguration
*/
private Boolean enabled;
/**
+ * Whether to allow to use resource template from header or not (default
+ * false). Enabling this allows to specify dynamic templates via message
+ * header. However this can be seen as a potential security vulnerability
if
+ * the header is coming from a malicious user, so use this with care.
+ */
+ private Boolean allowTemplateFromHeader = false;
+ /**
* 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
@@ -59,6 +66,14 @@ public class JsltComponentConfiguration
*/
private Collection<Function> functions;
+ public Boolean getAllowTemplateFromHeader() {
+ return allowTemplateFromHeader;
+ }
+
+ public void setAllowTemplateFromHeader(Boolean allowTemplateFromHeader) {
+ this.allowTemplateFromHeader = allowTemplateFromHeader;
+ }
+
public Boolean getLazyStartProducer() {
return lazyStartProducer;
}
diff --git
a/components-starter/camel-mustache-starter/src/main/docs/mustache-starter.adoc
b/components-starter/camel-mustache-starter/src/main/docs/mustache-starter.adoc
index e0c0bfb..163b822 100644
---
a/components-starter/camel-mustache-starter/src/main/docs/mustache-starter.adoc
+++
b/components-starter/camel-mustache-starter/src/main/docs/mustache-starter.adoc
@@ -17,17 +17,17 @@ When using mustache with Spring Boot make sure to use the
following Maven depend
----
-The component supports 4 options, which are listed below.
+The component supports 5 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.mustache.allow-template-from-header* | Whether to allow to
use resource template from header or not (default false). Enabling this allows
to specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.mustache.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.mustache.enabled* | Whether to enable auto configuration of
the mustache component. This is enabled by default. | | Boolean
| *camel.component.mustache.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 t [...]
| *camel.component.mustache.mustache-factory* | To use a custom
MustacheFactory. The option is a com.github.mustachejava.MustacheFactory type.
| | String
|===
-
// spring-boot-auto-configure options: END
diff --git
a/components-starter/camel-mustache-starter/src/main/java/org/apache/camel/component/mustache/springboot/MustacheComponentConfiguration.java
b/components-starter/camel-mustache-starter/src/main/java/org/apache/camel/component/mustache/springboot/MustacheComponentConfiguration.java
index 42e7787..c37438d 100644
---
a/components-starter/camel-mustache-starter/src/main/java/org/apache/camel/component/mustache/springboot/MustacheComponentConfiguration.java
+++
b/components-starter/camel-mustache-starter/src/main/java/org/apache/camel/component/mustache/springboot/MustacheComponentConfiguration.java
@@ -37,6 +37,13 @@ public class MustacheComponentConfiguration
*/
private Boolean enabled;
/**
+ * Whether to allow to use resource template from header or not (default
+ * false). Enabling this allows to specify dynamic templates via message
+ * header. However this can be seen as a potential security vulnerability
if
+ * the header is coming from a malicious user, so use this with care.
+ */
+ private Boolean allowTemplateFromHeader = false;
+ /**
* 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
@@ -58,6 +65,14 @@ public class MustacheComponentConfiguration
*/
private String mustacheFactory;
+ public Boolean getAllowTemplateFromHeader() {
+ return allowTemplateFromHeader;
+ }
+
+ public void setAllowTemplateFromHeader(Boolean allowTemplateFromHeader) {
+ this.allowTemplateFromHeader = allowTemplateFromHeader;
+ }
+
public Boolean getLazyStartProducer() {
return lazyStartProducer;
}
diff --git
a/components-starter/camel-mvel-starter/src/main/docs/mvel-starter.adoc
b/components-starter/camel-mvel-starter/src/main/docs/mvel-starter.adoc
index 01268ca..2206d09 100644
--- a/components-starter/camel-mvel-starter/src/main/docs/mvel-starter.adoc
+++ b/components-starter/camel-mvel-starter/src/main/docs/mvel-starter.adoc
@@ -17,18 +17,18 @@ When using mvel with Spring Boot make sure to use the
following Maven dependency
----
-The component supports 5 options, which are listed below.
+The component supports 6 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.mvel.allow-template-from-header* | Whether to allow to use
resource template from header or not (default false). Enabling this allows to
specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.mvel.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.mvel.enabled* | Whether to enable auto configuration of the
mvel component. This is enabled by default. | | Boolean
| *camel.component.mvel.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 [...]
| *camel.language.mvel.enabled* | Whether to enable auto configuration of the
mvel language. This is enabled by default. | | Boolean
| *camel.language.mvel.trim* | Whether to trim the value to remove leading and
trailing whitespaces and line breaks | true | Boolean
|===
-
// spring-boot-auto-configure options: END
diff --git
a/components-starter/camel-mvel-starter/src/main/java/org/apache/camel/component/mvel/springboot/MvelComponentConfiguration.java
b/components-starter/camel-mvel-starter/src/main/java/org/apache/camel/component/mvel/springboot/MvelComponentConfiguration.java
index a635419..fc07092 100644
---
a/components-starter/camel-mvel-starter/src/main/java/org/apache/camel/component/mvel/springboot/MvelComponentConfiguration.java
+++
b/components-starter/camel-mvel-starter/src/main/java/org/apache/camel/component/mvel/springboot/MvelComponentConfiguration.java
@@ -37,6 +37,13 @@ public class MvelComponentConfiguration
*/
private Boolean enabled;
/**
+ * Whether to allow to use resource template from header or not (default
+ * false). Enabling this allows to specify dynamic templates via message
+ * header. However this can be seen as a potential security vulnerability
if
+ * the header is coming from a malicious user, so use this with care.
+ */
+ private Boolean allowTemplateFromHeader = false;
+ /**
* 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
@@ -53,6 +60,14 @@ public class MvelComponentConfiguration
*/
private Boolean basicPropertyBinding = false;
+ public Boolean getAllowTemplateFromHeader() {
+ return allowTemplateFromHeader;
+ }
+
+ public void setAllowTemplateFromHeader(Boolean allowTemplateFromHeader) {
+ this.allowTemplateFromHeader = allowTemplateFromHeader;
+ }
+
public Boolean getLazyStartProducer() {
return lazyStartProducer;
}
diff --git
a/components-starter/camel-robotframework-starter/src/main/docs/robotframework-starter.adoc
b/components-starter/camel-robotframework-starter/src/main/docs/robotframework-starter.adoc
index ac3aee8..c087b7d 100644
---
a/components-starter/camel-robotframework-starter/src/main/docs/robotframework-starter.adoc
+++
b/components-starter/camel-robotframework-starter/src/main/docs/robotframework-starter.adoc
@@ -17,13 +17,14 @@ When using robotframework with Spring Boot make sure to use
the following Maven
----
-The component supports 50 options, which are listed below.
+The component supports 51 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.robotframework.allow-template-from-header* | Whether to
allow to use resource template from header or not (default false). Enabling
this allows to specify dynamic templates via message header. However this can
be seen as a potential security vulnerability if the header is coming from a
malicious user, so use this with care. | false | Boolean
| *camel.component.robotframework.argument-file* | A text file to read more
arguments from. | | File
| *camel.component.robotframework.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.robotframework.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
diff --git
a/components-starter/camel-robotframework-starter/src/main/java/org/apache/camel/component/robotframework/springboot/RobotFrameworkComponentConfiguration.java
b/components-starter/camel-robotframework-starter/src/main/java/org/apache/camel/component/robotframework/springboot/RobotFrameworkComponentConfiguration.java
index 8d123af..60147eb 100644
---
a/components-starter/camel-robotframework-starter/src/main/java/org/apache/camel/component/robotframework/springboot/RobotFrameworkComponentConfiguration.java
+++
b/components-starter/camel-robotframework-starter/src/main/java/org/apache/camel/component/robotframework/springboot/RobotFrameworkComponentConfiguration.java
@@ -38,6 +38,13 @@ public class RobotFrameworkComponentConfiguration
*/
private Boolean enabled;
/**
+ * Whether to allow to use resource template from header or not (default
+ * false). Enabling this allows to specify dynamic templates via message
+ * header. However this can be seen as a potential security vulnerability
if
+ * the header is coming from a malicious user, so use this with care.
+ */
+ private Boolean allowTemplateFromHeader = false;
+ /**
* A text file to read more arguments from.
*/
private File argumentFile;
@@ -268,6 +275,14 @@ public class RobotFrameworkComponentConfiguration
*/
private String configuration;
+ public Boolean getAllowTemplateFromHeader() {
+ return allowTemplateFromHeader;
+ }
+
+ public void setAllowTemplateFromHeader(Boolean allowTemplateFromHeader) {
+ this.allowTemplateFromHeader = allowTemplateFromHeader;
+ }
+
public File getArgumentFile() {
return argumentFile;
}
diff --git
a/components-starter/camel-stringtemplate-starter/src/main/docs/stringtemplate-starter.adoc
b/components-starter/camel-stringtemplate-starter/src/main/docs/stringtemplate-starter.adoc
index ba4780d..4397314 100644
---
a/components-starter/camel-stringtemplate-starter/src/main/docs/stringtemplate-starter.adoc
+++
b/components-starter/camel-stringtemplate-starter/src/main/docs/stringtemplate-starter.adoc
@@ -17,16 +17,16 @@ When using stringtemplate with Spring Boot make sure to use
the following Maven
----
-The component supports 3 options, which are listed below.
+The component supports 4 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.string-template.allow-template-from-header* | Whether to
allow to use resource template from header or not (default false). Enabling
this allows to specify dynamic templates via message header. However this can
be seen as a potential security vulnerability if the header is coming from a
malicious user, so use this with care. | false | Boolean
| *camel.component.string-template.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.string-template.enabled* | Whether to enable auto
configuration of the string-template component. This is enabled by default. |
| Boolean
| *camel.component.string-template.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 proc [...]
|===
-
// spring-boot-auto-configure options: END
diff --git
a/components-starter/camel-stringtemplate-starter/src/main/java/org/apache/camel/component/stringtemplate/springboot/StringTemplateComponentConfiguration.java
b/components-starter/camel-stringtemplate-starter/src/main/java/org/apache/camel/component/stringtemplate/springboot/StringTemplateComponentConfiguration.java
index 5a712d3..fe67576 100644
---
a/components-starter/camel-stringtemplate-starter/src/main/java/org/apache/camel/component/stringtemplate/springboot/StringTemplateComponentConfiguration.java
+++
b/components-starter/camel-stringtemplate-starter/src/main/java/org/apache/camel/component/stringtemplate/springboot/StringTemplateComponentConfiguration.java
@@ -37,6 +37,13 @@ public class StringTemplateComponentConfiguration
*/
private Boolean enabled;
/**
+ * Whether to allow to use resource template from header or not (default
+ * false). Enabling this allows to specify dynamic templates via message
+ * header. However this can be seen as a potential security vulnerability
if
+ * the header is coming from a malicious user, so use this with care.
+ */
+ private Boolean allowTemplateFromHeader = false;
+ /**
* 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
@@ -53,6 +60,14 @@ public class StringTemplateComponentConfiguration
*/
private Boolean basicPropertyBinding = false;
+ public Boolean getAllowTemplateFromHeader() {
+ return allowTemplateFromHeader;
+ }
+
+ public void setAllowTemplateFromHeader(Boolean allowTemplateFromHeader) {
+ this.allowTemplateFromHeader = allowTemplateFromHeader;
+ }
+
public Boolean getLazyStartProducer() {
return lazyStartProducer;
}
diff --git
a/components-starter/camel-velocity-starter/src/main/docs/velocity-starter.adoc
b/components-starter/camel-velocity-starter/src/main/docs/velocity-starter.adoc
index 8bded3b..7d88354 100644
---
a/components-starter/camel-velocity-starter/src/main/docs/velocity-starter.adoc
+++
b/components-starter/camel-velocity-starter/src/main/docs/velocity-starter.adoc
@@ -17,17 +17,17 @@ When using velocity with Spring Boot make sure to use the
following Maven depend
----
-The component supports 4 options, which are listed below.
+The component supports 5 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.velocity.allow-template-from-header* | Whether to allow to
use resource template from header or not (default false). Enabling this allows
to specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.velocity.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.velocity.enabled* | Whether to enable auto configuration of
the velocity component. This is enabled by default. | | Boolean
| *camel.component.velocity.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 t [...]
| *camel.component.velocity.velocity-engine* | To use the VelocityEngine
otherwise a new engine is created. The option is a
org.apache.velocity.app.VelocityEngine type. | | String
|===
-
// spring-boot-auto-configure options: END
diff --git
a/components-starter/camel-velocity-starter/src/main/java/org/apache/camel/component/velocity/springboot/VelocityComponentConfiguration.java
b/components-starter/camel-velocity-starter/src/main/java/org/apache/camel/component/velocity/springboot/VelocityComponentConfiguration.java
index 3246f33..57e31d7 100644
---
a/components-starter/camel-velocity-starter/src/main/java/org/apache/camel/component/velocity/springboot/VelocityComponentConfiguration.java
+++
b/components-starter/camel-velocity-starter/src/main/java/org/apache/camel/component/velocity/springboot/VelocityComponentConfiguration.java
@@ -37,6 +37,13 @@ public class VelocityComponentConfiguration
*/
private Boolean enabled;
/**
+ * Whether to allow to use resource template from header or not (default
+ * false). Enabling this allows to specify dynamic templates via message
+ * header. However this can be seen as a potential security vulnerability
if
+ * the header is coming from a malicious user, so use this with care.
+ */
+ private Boolean allowTemplateFromHeader = false;
+ /**
* 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
@@ -58,6 +65,14 @@ public class VelocityComponentConfiguration
*/
private String velocityEngine;
+ public Boolean getAllowTemplateFromHeader() {
+ return allowTemplateFromHeader;
+ }
+
+ public void setAllowTemplateFromHeader(Boolean allowTemplateFromHeader) {
+ this.allowTemplateFromHeader = allowTemplateFromHeader;
+ }
+
public Boolean getLazyStartProducer() {
return lazyStartProducer;
}
diff --git a/components-starter/pom.xml b/components-starter/pom.xml
index 3fbed80..aae3cd3 100644
--- a/components-starter/pom.xml
+++ b/components-starter/pom.xml
@@ -405,6 +405,7 @@
<module>camel-twilio-starter</module>
<module>camel-twitter-starter</module>
<module>camel-undertow-starter</module>
+ <module>camel-undertow-spring-security-starter</module>
<module>camel-univocity-parsers-starter</module>
<module>camel-validator-starter</module>
<module>camel-velocity-starter</module>
diff --git a/docs/modules/ROOT/pages/chunk-starter.adoc
b/docs/modules/ROOT/pages/chunk-starter.adoc
index 9d775c3..69f708d 100644
--- a/docs/modules/ROOT/pages/chunk-starter.adoc
+++ b/docs/modules/ROOT/pages/chunk-starter.adoc
@@ -17,16 +17,16 @@ When using chunk with Spring Boot make sure to use the
following Maven dependenc
----
-The component supports 3 options, which are listed below.
+The component supports 4 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.chunk.allow-template-from-header* | Whether to allow to use
resource template from header or not (default false). Enabling this allows to
specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.chunk.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.chunk.enabled* | Whether to enable auto configuration of
the chunk component. This is enabled by default. | | Boolean
| *camel.component.chunk.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 [...]
|===
-
// spring-boot-auto-configure options: END
diff --git a/docs/modules/ROOT/pages/jolt-starter.adoc
b/docs/modules/ROOT/pages/jolt-starter.adoc
index ba78cf4..2103a02 100644
--- a/docs/modules/ROOT/pages/jolt-starter.adoc
+++ b/docs/modules/ROOT/pages/jolt-starter.adoc
@@ -17,17 +17,17 @@ When using jolt with Spring Boot make sure to use the
following Maven dependency
----
-The component supports 4 options, which are listed below.
+The component supports 5 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.jolt.allow-template-from-header* | Whether to allow to use
resource template from header or not (default false). Enabling this allows to
specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.jolt.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.jolt.enabled* | Whether to enable auto configuration of the
jolt component. This is enabled by default. | | Boolean
| *camel.component.jolt.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 [...]
| *camel.component.jolt.transform* | Explicitly sets the Transform to use. If
not set a Transform specified by the transformDsl will be created. The option
is a com.bazaarvoice.jolt.Transform type. | | String
|===
-
// spring-boot-auto-configure options: END
diff --git a/docs/modules/ROOT/pages/jslt-starter.adoc
b/docs/modules/ROOT/pages/jslt-starter.adoc
index 3fd0119..aef4d34 100644
--- a/docs/modules/ROOT/pages/jslt-starter.adoc
+++ b/docs/modules/ROOT/pages/jslt-starter.adoc
@@ -17,17 +17,17 @@ When using jslt with Spring Boot make sure to use the
following Maven dependency
----
-The component supports 4 options, which are listed below.
+The component supports 5 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.jslt.allow-template-from-header* | Whether to allow to use
resource template from header or not (default false). Enabling this allows to
specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.jslt.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.jslt.enabled* | Whether to enable auto configuration of the
jslt component. This is enabled by default. | | Boolean
| *camel.component.jslt.functions* | JSLT can be extended by plugging in
functions written in Java. | | Collection
| *camel.component.jslt.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 [...]
|===
-
// spring-boot-auto-configure options: END
diff --git a/docs/modules/ROOT/pages/list.adoc
b/docs/modules/ROOT/pages/list.adoc
index 40e8707..cc2bb05 100644
--- a/docs/modules/ROOT/pages/list.adoc
+++ b/docs/modules/ROOT/pages/list.adoc
@@ -1213,7 +1213,7 @@ Number of Camel languages: 17 in 11 JAR artifacts (0
deprecated)
== Miscellaneous Extensions
// others: START
-Number of miscellaneous extensions: 22 in 22 JAR artifacts (0 deprecated)
+Number of miscellaneous extensions: 23 in 23 JAR artifacts (0 deprecated)
[width="100%",cols="4,1,5",options="header"]
|===
@@ -1282,6 +1282,9 @@ Number of miscellaneous extensions: 22 in 22 JAR
artifacts (0 deprecated)
|
link:https://camel.apache.org/components/latest/others/swagger-java.html[Swagger
Java] +
(camel-swagger-java-starter) | 2.16 | Rest-dsl support for using swagger
api-doc
+|
link:https://camel.apache.org/components/latest/others/undertow-spring-security.html[Undertow
Spring Security] +
+(camel-undertow-spring-security-starter) | 3.3 | Spring Security Provider for
camel-undertow
+
| link:https://camel.apache.org/components/latest/others/zipkin.html[Zipkin] +
(camel-zipkin-starter) | 2.18 | Distributed message tracing using Zipkin
|===
diff --git a/docs/modules/ROOT/pages/mustache-starter.adoc
b/docs/modules/ROOT/pages/mustache-starter.adoc
index e0c0bfb..163b822 100644
--- a/docs/modules/ROOT/pages/mustache-starter.adoc
+++ b/docs/modules/ROOT/pages/mustache-starter.adoc
@@ -17,17 +17,17 @@ When using mustache with Spring Boot make sure to use the
following Maven depend
----
-The component supports 4 options, which are listed below.
+The component supports 5 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.mustache.allow-template-from-header* | Whether to allow to
use resource template from header or not (default false). Enabling this allows
to specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.mustache.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.mustache.enabled* | Whether to enable auto configuration of
the mustache component. This is enabled by default. | | Boolean
| *camel.component.mustache.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 t [...]
| *camel.component.mustache.mustache-factory* | To use a custom
MustacheFactory. The option is a com.github.mustachejava.MustacheFactory type.
| | String
|===
-
// spring-boot-auto-configure options: END
diff --git a/docs/modules/ROOT/pages/mvel-starter.adoc
b/docs/modules/ROOT/pages/mvel-starter.adoc
index 01268ca..2206d09 100644
--- a/docs/modules/ROOT/pages/mvel-starter.adoc
+++ b/docs/modules/ROOT/pages/mvel-starter.adoc
@@ -17,18 +17,18 @@ When using mvel with Spring Boot make sure to use the
following Maven dependency
----
-The component supports 5 options, which are listed below.
+The component supports 6 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.mvel.allow-template-from-header* | Whether to allow to use
resource template from header or not (default false). Enabling this allows to
specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.mvel.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.mvel.enabled* | Whether to enable auto configuration of the
mvel component. This is enabled by default. | | Boolean
| *camel.component.mvel.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 [...]
| *camel.language.mvel.enabled* | Whether to enable auto configuration of the
mvel language. This is enabled by default. | | Boolean
| *camel.language.mvel.trim* | Whether to trim the value to remove leading and
trailing whitespaces and line breaks | true | Boolean
|===
-
// spring-boot-auto-configure options: END
diff --git a/docs/modules/ROOT/pages/robotframework-starter.adoc
b/docs/modules/ROOT/pages/robotframework-starter.adoc
index ac3aee8..c087b7d 100644
--- a/docs/modules/ROOT/pages/robotframework-starter.adoc
+++ b/docs/modules/ROOT/pages/robotframework-starter.adoc
@@ -17,13 +17,14 @@ When using robotframework with Spring Boot make sure to use
the following Maven
----
-The component supports 50 options, which are listed below.
+The component supports 51 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.robotframework.allow-template-from-header* | Whether to
allow to use resource template from header or not (default false). Enabling
this allows to specify dynamic templates via message header. However this can
be seen as a potential security vulnerability if the header is coming from a
malicious user, so use this with care. | false | Boolean
| *camel.component.robotframework.argument-file* | A text file to read more
arguments from. | | File
| *camel.component.robotframework.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.robotframework.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
diff --git a/docs/modules/ROOT/pages/stringtemplate-starter.adoc
b/docs/modules/ROOT/pages/stringtemplate-starter.adoc
index ba4780d..4397314 100644
--- a/docs/modules/ROOT/pages/stringtemplate-starter.adoc
+++ b/docs/modules/ROOT/pages/stringtemplate-starter.adoc
@@ -17,16 +17,16 @@ When using stringtemplate with Spring Boot make sure to use
the following Maven
----
-The component supports 3 options, which are listed below.
+The component supports 4 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.string-template.allow-template-from-header* | Whether to
allow to use resource template from header or not (default false). Enabling
this allows to specify dynamic templates via message header. However this can
be seen as a potential security vulnerability if the header is coming from a
malicious user, so use this with care. | false | Boolean
| *camel.component.string-template.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.string-template.enabled* | Whether to enable auto
configuration of the string-template component. This is enabled by default. |
| Boolean
| *camel.component.string-template.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 proc [...]
|===
-
// spring-boot-auto-configure options: END
diff --git a/docs/modules/ROOT/pages/undertow-spring-security-starter.adoc
b/docs/modules/ROOT/pages/undertow-spring-security-starter.adoc
new file mode 100644
index 0000000..3a4db8a
--- /dev/null
+++ b/docs/modules/ROOT/pages/undertow-spring-security-starter.adoc
@@ -0,0 +1,33 @@
+// spring-boot-auto-configure options: START
+:page-partial:
+:doctitle: Camel Spring Boot Starter for undertow-spring-security
+
+== Spring Boot Auto-Configuration
+
+When using undertow-spring-security 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-undertow-spring-security-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.undertow.spring.security.keycloak* | Properties defined for
keycloak provider. Value is gathered together from properties with prefix
"camel.component.undertow.spring.security.keycloak" | |
KeycloakProviderConfiguration
+| *camel.component.undertow.spring.security.keycloak.client-id* | Client id
from the Keycloak server used for authentication. | | String
+| *camel.component.undertow.spring.security.keycloak.realm-id* | Realm id from
the keycloak server used for authentication. | | String
+| *camel.component.undertow.spring.security.keycloak.url* | Url to keycloak
server which will be used in spring security configuration. (Example
"\http://localhost:8080";) | | String
+| *camel.component.undertow.spring.security.keycloak.user-name-attribute* |
Name of the attribute, which will be used as username. | preffered_username |
String
+|===
+// spring-boot-auto-configure options: END
diff --git a/docs/modules/ROOT/pages/velocity-starter.adoc
b/docs/modules/ROOT/pages/velocity-starter.adoc
index 8bded3b..7d88354 100644
--- a/docs/modules/ROOT/pages/velocity-starter.adoc
+++ b/docs/modules/ROOT/pages/velocity-starter.adoc
@@ -17,17 +17,17 @@ When using velocity with Spring Boot make sure to use the
following Maven depend
----
-The component supports 4 options, which are listed below.
+The component supports 5 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
+| *camel.component.velocity.allow-template-from-header* | Whether to allow to
use resource template from header or not (default false). Enabling this allows
to specify dynamic templates via message header. However this can be seen as a
potential security vulnerability if the header is coming from a malicious user,
so use this with care. | false | Boolean
| *camel.component.velocity.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.velocity.enabled* | Whether to enable auto configuration of
the velocity component. This is enabled by default. | | Boolean
| *camel.component.velocity.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 t [...]
| *camel.component.velocity.velocity-engine* | To use the VelocityEngine
otherwise a new engine is created. The option is a
org.apache.velocity.app.VelocityEngine type. | | String
|===
-
// spring-boot-auto-configure options: END
diff --git a/tooling/camel-spring-boot-dependencies/pom.xml
b/tooling/camel-spring-boot-dependencies/pom.xml
index c03f109..32881b7 100644
--- a/tooling/camel-spring-boot-dependencies/pom.xml
+++ b/tooling/camel-spring-boot-dependencies/pom.xml
@@ -768,11 +768,6 @@
</dependency>
<dependency>
<groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-elytron-starter</artifactId>
- <version>${project.version}</version>
- </dependency>
- <dependency>
- <groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-etcd-starter</artifactId>
<version>${project.version}</version>
</dependency>
@@ -1158,11 +1153,6 @@
</dependency>
<dependency>
<groupId>org.apache.camel.springboot</groupId>
- <artifactId>camel-kura-starter</artifactId>
- <version>${project.version}</version>
- </dependency>
- <dependency>
- <groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-language-starter</artifactId>
<version>${project.version}</version>
</dependency>
