Return-Path: X-Original-To: apmail-camel-commits-archive@www.apache.org Delivered-To: apmail-camel-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9A7CFE313 for ; Fri, 18 Jan 2013 13:26:19 +0000 (UTC) Received: (qmail 20536 invoked by uid 500); 18 Jan 2013 13:26:19 -0000 Delivered-To: apmail-camel-commits-archive@camel.apache.org Received: (qmail 20385 invoked by uid 500); 18 Jan 2013 13:26:18 -0000 Mailing-List: contact commits-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list commits@camel.apache.org Received: (qmail 20355 invoked by uid 99); 18 Jan 2013 13:26:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2013 13:26:17 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2013 13:26:14 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 494F923889BB for ; Fri, 18 Jan 2013 13:25:55 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r847158 - in /websites/production/camel/content: book-component-appendix.html sql-component.html Date: Fri, 18 Jan 2013 13:25:55 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20130118132555.494F923889BB@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Fri Jan 18 13:25:54 2013 New Revision: 847158 Log: Production update by buildbot for camel Modified: websites/production/camel/content/book-component-appendix.html websites/production/camel/content/sql-component.html Modified: websites/production/camel/content/book-component-appendix.html ============================================================================== --- websites/production/camel/content/book-component-appendix.html (original) +++ websites/production/camel/content/book-component-appendix.html Fri Jan 18 13:25:54 2013 @@ -16312,7 +16312,7 @@ sql:select * from table where id=:#myId

Options

-

Option	Type	Default	Description
`batch`	`boolean`	`false`	Camel 2.7.5, 2.8.4 and 2.9: Execute SQL batch update statements. See notes below on how the treatment of the inbound message body changes if this is set to `true`.
`dataSourceRef`	`String`	`null`	Reference to a `DataSource` to look up in the registry.
`placeholder`	`String`	`#`	Camel 2.4: Specifies a character that will be replaced to `?` in SQL query. Notice, that it is simple `String.replaceAll()` operation and no SQL parsing is involved (quoted strings will also change). This replacement is only happening if the endpoint is created using the `SqlComponent`. If you manually create the endpoint, then use the expected `?` sign instead.
`template.<xxx>`		`null`	Sets additional options on the Spring `JdbcTemplate` that is used behind the scenes to execute the queries. For instance, `template.maxRows=10`. For detailed documentation, see the JdbcTemplate javadoc documentation.
`allowNamedParameters`	`boolean`	`true`	Camel 2.11: Whether to allow using named parameters in the queries.
`processingStrategy`	< /td>		Camel 2.11: SQL consumer only: Allows to plugin to use a custom `org.apache.camel.component.sql.SqlProcessingStrategy` to execute queries when the consumer has processed the rows/batch.
`prepareStatementStrategy`			Camel 2.11: Allows to plugin to use a custom `org.apache.camel.component.sql.SqlPrepareStatementStrategy` to control preparation of the query and prepared statement.
`consumer.delay`	`long`	`500`	Camel 2.11: SQL consumer only: Delay in milliseconds between each poll.
`consumer.initialDelay`	`long`	`1000`	Camel 2.11: SQL consumer only: Milliseconds before polling starts.
`consumer.useFixedDelay`	`boolean`	`false`	Camel 2.11: SQL consumer only: Set to `true` to use fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
`maxMessagesPerPoll`	`int`	`0`	Camel 2.11: SQL consumer only: An integer value to define the maximum number of messages to gather per poll. By default, no maximum is set.
`consumer.useIterator`	`boolean`	`true`	Camel 2.11: SQL consumer only: If `true` each row returned when polling will be proce ssed individually. If `false` the entire `java.util.List` of data is set as the IN body.
`consumer.routeEmptyResultSet`	`boolean`	`false`	Camel 2.11: SQL consumer only: Whether to route a single empty Exchange if there was no data to poll.
`consumer.onConsume`	`String`	`null`	Camel 2.11: SQL consumer only: After processing each row then this query can be executed to for example delete or mark the row as processed. The query can have parameter.
`consumer.onConsumeBatchComplete`	`String`	`null`	Camel 2.11: SQL consumer only: After processing the entire batch, this query can be executed to bulk update rows etc. The query cannot have parameters.
`consumer.expectedUpdateCount`	`int`	`-1`	Camel 2.11: SQL consumer only: If using `consumer.onConsume` then this option can be used to set an expected number of rows being updated. Typically you may set this to `1` to expect one row to be updated.
`consumer.breakBatchOnConsumeFail`	`boolean`	`false`	Camel 2.11: SQL consumer only: If using `consumer.onConsume` and it fails, then this option controls whether to break out of the batch or continue processing the next row from the batch.

+

Option	Type	Default	Description
`batch`	`boolean`	`false`	Camel 2.7.5, 2.8.4 and 2.9: Execute SQL batch update statements. See notes below on how the treatment of the inbound message body changes if this is set to `true`.
`dataSourceRef`	`String`	`null`	Reference to a `DataSource` to look up in the registry.
`placeholder`	`String`	`#`	Camel 2.4: Specifies a character that will be replaced to `?` in SQL query. Notice, that it is simple `String.replaceAll()` operation and no SQL parsing is involved (quoted strings will also change). This replacement is only happening if the endpoint is created using the `SqlComponent`. If you manually create the endpoint, then use the expected `?` sign instead.
`template.<xxx>`		`null`	Sets additional options on the Spring `JdbcTemplate` that is used behind the scenes to execute the queries. For instance, `template.maxRows=10`. For detailed documentation, see the JdbcTemplate javadoc documentation.
`allowNamedParameters`	`boolean`	`true`	Camel 2.11: Whether to allow using named parameters in the queries.
`processingStrategy`	< /td>		Camel 2.11: SQL consumer only: Allows to plugin to use a custom `org.apache.camel.component.sql.SqlProcessingStrategy` to execute queries when the consumer has processed the rows/batch.
`prepareStatementStrategy`			Camel 2.11: Allows to plugin to use a custom `org.apache.camel.component.sql.SqlPrepareStatementStrategy` to control preparation of the query and prepared statement.
`consumer.delay`	`long`	`500`	Camel 2.11: SQL consumer only: Delay in milliseconds between each poll.
`consumer.initialDelay`	`long`	`1000`	Camel 2.11: SQL consumer only: Milliseconds before polling starts.
`consumer.useFixedDelay`	`boolean`	`false`	Camel 2.11: SQL consumer only: Set to `true` to use fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
`maxMessagesPerPoll`	`int`	`0`	Camel 2.11: SQL consumer only: An integer value to define the maximum number of messages to gather per poll. By default, no maximum is set.
`consumer.useIterator`	`boolean`	`true`	Camel 2.11: SQL consumer only: If `true` each row returned when polling will be proce ssed individually. If `false` the entire `java.util.List` of data is set as the IN body.
`consumer.routeEmptyResultSet`	`boolean`	`false`	Camel 2.11: SQL consumer only: Whether to route a single empty Exchange if there was no data to poll.
`consumer.onConsume`	`String`	`null`	Camel 2.11: SQL consumer only: After processing each row then this query can be executed, if the Exchange was processed successfully, for example to mark the row as processed. The query can have parameter.
`consumer.onConsumeFailed`	`String`	`null`	Camel 2.11: SQL consumer only: After processing each row then this query can be executed, if the Exchange failed, for example to mark the row as failed. The query can have parameter.
`consumer.onConsumeBatchComplete`	`String`	`null`	Camel 2.11: SQL consumer only: After processing the entire batch, this query can be executed to bulk update rows etc. The query cannot have parameters.
`consumer.expectedUpdateCount`	`int`	`-1`	Camel 2.11: SQL consumer only: If using `consumer.onConsume` then this option can be used to set an expected number of rows being updated. Typically you may set this to `1` to expect one row to be updated.
`consumer.breakBatchOnConsumeFail`	`boolean`	`false`	Camel 2.11: SQL consumer only: If using `consumer.onConsume` and it fails, then this option controls whether to break out of the batch or continue processing the next row from the batch.

Modified: websites/production/camel/content/sql-component.html ============================================================================== --- websites/production/camel/content/sql-component.html (original) +++ websites/production/camel/content/sql-component.html Fri Jan 18 13:25:54 2013 @@ -132,7 +132,7 @@ sql:select * from table where id=:#myId

Options

-

Option	Type	Default	Description
`batch`	`boolean`	`false`	Camel 2.7.5, 2.8.4 and 2.9: Execute SQL batch update statements. See notes below on how the treatment of the inbound message body changes if this is set to `true`.
`dataSourceRef`	`String`	`null`	Reference to a `DataSource` to look up in the registry.
`placeholder`	`String`	`#`	Camel 2.4: Specifies a character that will be replaced to `?` in SQL query. Notice, that it is simple `String.replaceAll()` operation and no SQL parsing is involved (quoted strings will also change). This replacement is only happening if the endpoint is created using the `SqlComponent`. If you manually create the endpoint, then use the expected `?` sign instead.
`template.<xxx>`		`null`	Sets additional options on the Spring `JdbcTemplate` that is used behind the scenes to execute the queries. For instance, `template.maxRows=10`. For detailed documentation, see the JdbcTemplate javadoc documentation.
`allowNamedParameters`	`boolean`	`true`	Camel 2.11: Whether to allow using named parameters in the queries.
`processingStrategy`	< /td>		Camel 2.11: SQL consumer only: Allows to plugin to use a custom `org.apache.camel.component.sql.SqlProcessingStrategy` to execute queries when the consumer has processed the rows/batch.
`prepareStatementStrategy`			Camel 2.11: Allows to plugin to use a custom `org.apache.camel.component.sql.SqlPrepareStatementStrategy` to control preparation of the query and prepared statement.
`consumer.delay`	`long`	`500`	Camel 2.11: SQL consumer only: Delay in milliseconds between each poll.
`consumer.initialDelay`	`long`	`1000`	Camel 2.11: SQL consumer only: Milliseconds before polling starts.
`consumer.useFixedDelay`	`boolean`	`false`	Camel 2.11: SQL consumer only: Set to `true` to use fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
`maxMessagesPerPoll`	`int`	`0`	Camel 2.11: SQL consumer only: An integer value to define the maximum number of messages to gather per poll. By default, no maximum is set.
`consumer.useIterator`	`boolean`	`true`	Camel 2.11: SQL consumer only: If `true` each row returned when polling will be proce ssed individually. If `false` the entire `java.util.List` of data is set as the IN body.
`consumer.routeEmptyResultSet`	`boolean`	`false`	Camel 2.11: SQL consumer only: Whether to route a single empty Exchange if there was no data to poll.
`consumer.onConsume`	`String`	`null`	Camel 2.11: SQL consumer only: After processing each row then this query can be executed to for example delete or mark the row as processed. The query can have parameter.
`consumer.onConsumeBatchComplete`	`String`	`null`	Camel 2.11: SQL consumer only: After processing the entire batch, this query can be executed to bulk update rows etc. The query cannot have parameters.
`consumer.expectedUpdateCount`	`int`	`-1`	Camel 2.11: SQL consumer only: If using `consumer.onConsume` then this option can be used to set an expected number of rows being updated. Typically you may set this to `1` to expect one row to be updated.
`consumer.breakBatchOnConsumeFail`	`boolean`	`false`	Camel 2.11: SQL consumer only: If using `consumer.onConsume` and it fails, then this option controls whether to break out of the batch or continue processing the next row from the batch.

+

Option	Type	Default	Description
`batch`	`boolean`	`false`	Camel 2.7.5, 2.8.4 and 2.9: Execute SQL batch update statements. See notes below on how the treatment of the inbound message body changes if this is set to `true`.
`dataSourceRef`	`String`	`null`	Reference to a `DataSource` to look up in the registry.
`placeholder`	`String`	`#`	Camel 2.4: Specifies a character that will be replaced to `?` in SQL query. Notice, that it is simple `String.replaceAll()` operation and no SQL parsing is involved (quoted strings will also change). This replacement is only happening if the endpoint is created using the `SqlComponent`. If you manually create the endpoint, then use the expected `?` sign instead.
`template.<xxx>`		`null`	Sets additional options on the Spring `JdbcTemplate` that is used behind the scenes to execute the queries. For instance, `template.maxRows=10`. For detailed documentation, see the JdbcTemplate javadoc documentation.
`allowNamedParameters`	`boolean`	`true`	Camel 2.11: Whether to allow using named parameters in the queries.
`processingStrategy`	< /td>		Camel 2.11: SQL consumer only: Allows to plugin to use a custom `org.apache.camel.component.sql.SqlProcessingStrategy` to execute queries when the consumer has processed the rows/batch.
`prepareStatementStrategy`			Camel 2.11: Allows to plugin to use a custom `org.apache.camel.component.sql.SqlPrepareStatementStrategy` to control preparation of the query and prepared statement.
`consumer.delay`	`long`	`500`	Camel 2.11: SQL consumer only: Delay in milliseconds between each poll.
`consumer.initialDelay`	`long`	`1000`	Camel 2.11: SQL consumer only: Milliseconds before polling starts.
`consumer.useFixedDelay`	`boolean`	`false`	Camel 2.11: SQL consumer only: Set to `true` to use fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details.
`maxMessagesPerPoll`	`int`	`0`	Camel 2.11: SQL consumer only: An integer value to define the maximum number of messages to gather per poll. By default, no maximum is set.
`consumer.useIterator`	`boolean`	`true`	Camel 2.11: SQL consumer only: If `true` each row returned when polling will be proce ssed individually. If `false` the entire `java.util.List` of data is set as the IN body.
`consumer.routeEmptyResultSet`	`boolean`	`false`	Camel 2.11: SQL consumer only: Whether to route a single empty Exchange if there was no data to poll.
`consumer.onConsume`	`String`	`null`	Camel 2.11: SQL consumer only: After processing each row then this query can be executed, if the Exchange was processed successfully, for example to mark the row as processed. The query can have parameter.
`consumer.onConsumeFailed`	`String`	`null`	Camel 2.11: SQL consumer only: After processing each row then this query can be executed, if the Exchange failed, for example to mark the row as failed. The query can have parameter.
`consumer.onConsumeBatchComplete`	`String`	`null`	Camel 2.11: SQL consumer only: After processing the entire batch, this query can be executed to bulk update rows etc. The query cannot have parameters.
`consumer.expectedUpdateCount`	`int`	`-1`	Camel 2.11: SQL consumer only: If using `consumer.onConsume` then this option can be used to set an expected number of rows being updated. Typically you may set this to `1` to expect one row to be updated.
`consumer.breakBatchOnConsumeFail`	`boolean`	`false`	Camel 2.11: SQL consumer only: If using `consumer.onConsume` and it fails, then this option controls whether to break out of the batch or continue processing the next row from the batch.