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.git
The following commit(s) were added to refs/heads/master by this push:
new b1d3afd Regen
b1d3afd is described below
commit b1d3afda7252e018b42e40a32078ea9c75715c7a
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Sat Mar 14 13:28:22 2020 +0100
Regen
---
.../generated/resources/org/apache/camel/component/elsql/elsql.json | 2 +-
components/camel-elsql/src/main/docs/elsql-component.adoc | 2 +-
.../src/generated/resources/org/apache/camel/component/sql/sql.json | 2 +-
components/camel-sql/src/main/docs/sql-component.adoc | 2 +-
.../camel/builder/endpoint/dsl/ElsqlEndpointBuilderFactory.java | 4 ++--
.../apache/camel/builder/endpoint/dsl/SqlEndpointBuilderFactory.java | 4 ++--
docs/components/modules/ROOT/pages/elsql-component.adoc | 2 +-
docs/components/modules/ROOT/pages/sql-component.adoc | 2 +-
8 files changed, 10 insertions(+), 10 deletions(-)
diff --git
a/components/camel-elsql/src/generated/resources/org/apache/camel/component/elsql/elsql.json
b/components/camel-elsql/src/generated/resources/org/apache/camel/component/elsql/elsql.json
index 9ad5397..0872433 100644
---
a/components/camel-elsql/src/generated/resources/org/apache/camel/component/elsql/elsql.json
+++
b/components/camel-elsql/src/generated/resources/org/apache/camel/component/elsql/elsql.json
@@ -56,7 +56,7 @@
"batch": { "kind": "parameter", "displayName": "Batch", "group":
"producer", "label": "producer", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
false, "description": "Enables or disables batch mode" },
"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 [...]
"noop": { "kind": "parameter", "displayName": "Noop", "group": "producer",
"label": "producer", "required": false, "type": "boolean", "javaType":
"boolean", "deprecated": false, "secret": false, "defaultValue": false,
"description": "If set, will ignore the results of the SQL query and use the
existing IN message as the OUT message for the continuation of processing" },
- "useMessageBodyForSql": { "kind": "parameter", "displayName": "Use Message
Body For Sql", "group": "producer", "label": "producer", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used. Note that query parameters in the message body are
represented by a question ma [...]
+ "useMessageBodyForSql": { "kind": "parameter", "displayName": "Use Message
Body For Sql", "group": "producer", "label": "producer", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used.Note that query parameters in the message body are
represented by a question mar [...]
"alwaysPopulateStatement": { "kind": "parameter", "displayName": "Always
Populate Statement", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret":
false, "defaultValue": false, "description": "If enabled then the
populateStatement method from
org.apache.camel.component.sql.SqlPrepareStatementStrategy is always invoked,
also if there is no expected parameters to be prepared. When this is false then
the po [...]
"basicPropertyBinding": { "kind": "parameter", "displayName": "Basic
Property Binding", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether the endpoint should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities" },
"elSqlConfig": { "kind": "parameter", "displayName": "El Sql Config",
"group": "advanced", "label": "advanced", "required": false, "type": "object",
"javaType": "com.opengamma.elsql.ElSqlConfig", "deprecated": false, "secret":
false, "description": "To use a specific configured ElSqlConfig. It may be
better to use the databaseVendor option instead." },
diff --git a/components/camel-elsql/src/main/docs/elsql-component.adoc
b/components/camel-elsql/src/main/docs/elsql-component.adoc
index 7c123f1..354200b 100644
--- a/components/camel-elsql/src/main/docs/elsql-component.adoc
+++ b/components/camel-elsql/src/main/docs/elsql-component.adoc
@@ -125,7 +125,7 @@ with the following path and query parameters:
| *batch* (producer) | Enables or disables batch mode | false | boolean
| *lazyStartProducer* (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 creating and [...]
| *noop* (producer) | If set, will ignore the results of the SQL query and use
the existing IN message as the OUT message for the continuation of processing |
false | boolean
-| *useMessageBodyForSql* (producer) | Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used. Note that query parameters in the message body are
represented by a question mark instead of a # symbol. | false | boolean
+| *useMessageBodyForSql* (producer) | Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used.Note that query parameters in the message body are
represented by a question mark instead of a # symbol. | false | boolean
| *alwaysPopulateStatement* (advanced) | If enabled then the populateStatement
method from org.apache.camel.component.sql.SqlPrepareStatementStrategy is
always invoked, also if there is no expected parameters to be prepared. When
this is false then the populateStatement is only invoked if there is 1 or more
expected parameters to be set; for example this avoids reading the message
body/headers for SQL queries with no parameters. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the endpoint should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
| *elSqlConfig* (advanced) | To use a specific configured ElSqlConfig. It may
be better to use the databaseVendor option instead. | | ElSqlConfig
diff --git
a/components/camel-sql/src/generated/resources/org/apache/camel/component/sql/sql.json
b/components/camel-sql/src/generated/resources/org/apache/camel/component/sql/sql.json
index 8461ee3..7c6aaf0 100644
---
a/components/camel-sql/src/generated/resources/org/apache/camel/component/sql/sql.json
+++
b/components/camel-sql/src/generated/resources/org/apache/camel/component/sql/sql.json
@@ -52,7 +52,7 @@
"batch": { "kind": "parameter", "displayName": "Batch", "group":
"producer", "label": "producer", "required": false, "type": "boolean",
"javaType": "boolean", "deprecated": false, "secret": false, "defaultValue":
false, "description": "Enables or disables batch mode" },
"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 [...]
"noop": { "kind": "parameter", "displayName": "Noop", "group": "producer",
"label": "producer", "required": false, "type": "boolean", "javaType":
"boolean", "deprecated": false, "secret": false, "defaultValue": false,
"description": "If set, will ignore the results of the SQL query and use the
existing IN message as the OUT message for the continuation of processing" },
- "useMessageBodyForSql": { "kind": "parameter", "displayName": "Use Message
Body For Sql", "group": "producer", "label": "producer", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used. Note that query parameters in the message body are
represented by a question ma [...]
+ "useMessageBodyForSql": { "kind": "parameter", "displayName": "Use Message
Body For Sql", "group": "producer", "label": "producer", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used.Note that query parameters in the message body are
represented by a question mar [...]
"alwaysPopulateStatement": { "kind": "parameter", "displayName": "Always
Populate Statement", "group": "advanced", "label": "advanced", "required":
false, "type": "boolean", "javaType": "boolean", "deprecated": false, "secret":
false, "defaultValue": false, "description": "If enabled then the
populateStatement method from
org.apache.camel.component.sql.SqlPrepareStatementStrategy is always invoked,
also if there is no expected parameters to be prepared. When this is false then
the po [...]
"basicPropertyBinding": { "kind": "parameter", "displayName": "Basic
Property Binding", "group": "advanced", "label": "advanced", "required": false,
"type": "boolean", "javaType": "boolean", "deprecated": false, "secret": false,
"defaultValue": false, "description": "Whether the endpoint should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities" },
"parametersCount": { "kind": "parameter", "displayName": "Parameters
Count", "group": "advanced", "label": "advanced", "required": false, "type":
"integer", "javaType": "int", "deprecated": false, "secret": false,
"description": "If set greater than zero, then Camel will use this count value
of parameters to replace instead of querying via JDBC metadata API. This is
useful if the JDBC vendor could not return correct parameters count, then user
may override instead." },
diff --git a/components/camel-sql/src/main/docs/sql-component.adoc
b/components/camel-sql/src/main/docs/sql-component.adoc
index 282aea0..a47a93f 100644
--- a/components/camel-sql/src/main/docs/sql-component.adoc
+++ b/components/camel-sql/src/main/docs/sql-component.adoc
@@ -180,7 +180,7 @@ with the following path and query parameters:
| *batch* (producer) | Enables or disables batch mode | false | boolean
| *lazyStartProducer* (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 creating and [...]
| *noop* (producer) | If set, will ignore the results of the SQL query and use
the existing IN message as the OUT message for the continuation of processing |
false | boolean
-| *useMessageBodyForSql* (producer) | Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used. Note that query parameters in the message body are
represented by a question mark instead of a # symbol. | false | boolean
+| *useMessageBodyForSql* (producer) | Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used.Note that query parameters in the message body are
represented by a question mark instead of a # symbol. | false | boolean
| *alwaysPopulateStatement* (advanced) | If enabled then the populateStatement
method from org.apache.camel.component.sql.SqlPrepareStatementStrategy is
always invoked, also if there is no expected parameters to be prepared. When
this is false then the populateStatement is only invoked if there is 1 or more
expected parameters to be set; for example this avoids reading the message
body/headers for SQL queries with no parameters. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the endpoint should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
| *parametersCount* (advanced) | If set greater than zero, then Camel will use
this count value of parameters to replace instead of querying via JDBC metadata
API. This is useful if the JDBC vendor could not return correct parameters
count, then user may override instead. | | int
diff --git
a/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/ElsqlEndpointBuilderFactory.java
b/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/ElsqlEndpointBuilderFactory.java
index 6f195a5..84a0e98 100644
---
a/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/ElsqlEndpointBuilderFactory.java
+++
b/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/ElsqlEndpointBuilderFactory.java
@@ -1566,7 +1566,7 @@ public interface ElsqlEndpointBuilderFactory {
/**
* Whether to use the message body as the SQL and then headers for
* parameters. If this option is enabled then the SQL in the uri is not
- * used. Note that query parameters in the message body are represented
+ * used.Note that query parameters in the message body are represented
* by a question mark instead of a # symbol.
*
* The option is a: <code>boolean</code> type.
@@ -1582,7 +1582,7 @@ public interface ElsqlEndpointBuilderFactory {
/**
* Whether to use the message body as the SQL and then headers for
* parameters. If this option is enabled then the SQL in the uri is not
- * used. Note that query parameters in the message body are represented
+ * used.Note that query parameters in the message body are represented
* by a question mark instead of a # symbol.
*
* The option will be converted to a <code>boolean</code> type.
diff --git
a/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/SqlEndpointBuilderFactory.java
b/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/SqlEndpointBuilderFactory.java
index 4e3099e..3f96d2e 100644
---
a/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/SqlEndpointBuilderFactory.java
+++
b/core/camel-endpointdsl/src/generated/java/org/apache/camel/builder/endpoint/dsl/SqlEndpointBuilderFactory.java
@@ -1480,7 +1480,7 @@ public interface SqlEndpointBuilderFactory {
/**
* Whether to use the message body as the SQL and then headers for
* parameters. If this option is enabled then the SQL in the uri is not
- * used. Note that query parameters in the message body are represented
+ * used.Note that query parameters in the message body are represented
* by a question mark instead of a # symbol.
*
* The option is a: <code>boolean</code> type.
@@ -1496,7 +1496,7 @@ public interface SqlEndpointBuilderFactory {
/**
* Whether to use the message body as the SQL and then headers for
* parameters. If this option is enabled then the SQL in the uri is not
- * used. Note that query parameters in the message body are represented
+ * used.Note that query parameters in the message body are represented
* by a question mark instead of a # symbol.
*
* The option will be converted to a <code>boolean</code> type.
diff --git a/docs/components/modules/ROOT/pages/elsql-component.adoc
b/docs/components/modules/ROOT/pages/elsql-component.adoc
index 652bf2f..b58cd8e 100644
--- a/docs/components/modules/ROOT/pages/elsql-component.adoc
+++ b/docs/components/modules/ROOT/pages/elsql-component.adoc
@@ -126,7 +126,7 @@ with the following path and query parameters:
| *batch* (producer) | Enables or disables batch mode | false | boolean
| *lazyStartProducer* (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 creating and [...]
| *noop* (producer) | If set, will ignore the results of the SQL query and use
the existing IN message as the OUT message for the continuation of processing |
false | boolean
-| *useMessageBodyForSql* (producer) | Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used. Note that query parameters in the message body are
represented by a question mark instead of a # symbol. | false | boolean
+| *useMessageBodyForSql* (producer) | Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used.Note that query parameters in the message body are
represented by a question mark instead of a # symbol. | false | boolean
| *alwaysPopulateStatement* (advanced) | If enabled then the populateStatement
method from org.apache.camel.component.sql.SqlPrepareStatementStrategy is
always invoked, also if there is no expected parameters to be prepared. When
this is false then the populateStatement is only invoked if there is 1 or more
expected parameters to be set; for example this avoids reading the message
body/headers for SQL queries with no parameters. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the endpoint should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
| *elSqlConfig* (advanced) | To use a specific configured ElSqlConfig. It may
be better to use the databaseVendor option instead. | | ElSqlConfig
diff --git a/docs/components/modules/ROOT/pages/sql-component.adoc
b/docs/components/modules/ROOT/pages/sql-component.adoc
index 24c6fc7..d1f4b69 100644
--- a/docs/components/modules/ROOT/pages/sql-component.adoc
+++ b/docs/components/modules/ROOT/pages/sql-component.adoc
@@ -181,7 +181,7 @@ with the following path and query parameters:
| *batch* (producer) | Enables or disables batch mode | false | boolean
| *lazyStartProducer* (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 creating and [...]
| *noop* (producer) | If set, will ignore the results of the SQL query and use
the existing IN message as the OUT message for the continuation of processing |
false | boolean
-| *useMessageBodyForSql* (producer) | Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used. Note that query parameters in the message body are
represented by a question mark instead of a # symbol. | false | boolean
+| *useMessageBodyForSql* (producer) | Whether to use the message body as the
SQL and then headers for parameters. If this option is enabled then the SQL in
the uri is not used.Note that query parameters in the message body are
represented by a question mark instead of a # symbol. | false | boolean
| *alwaysPopulateStatement* (advanced) | If enabled then the populateStatement
method from org.apache.camel.component.sql.SqlPrepareStatementStrategy is
always invoked, also if there is no expected parameters to be prepared. When
this is false then the populateStatement is only invoked if there is 1 or more
expected parameters to be set; for example this avoids reading the message
body/headers for SQL queries with no parameters. | false | boolean
| *basicPropertyBinding* (advanced) | Whether the endpoint should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
| *parametersCount* (advanced) | If set greater than zero, then Camel will use
this count value of parameters to replace instead of querying via JDBC metadata
API. This is useful if the JDBC vendor could not return correct parameters
count, then user may override instead. | | int
