Option | Type | Default | Description |
---|
resourceUri | String | null | Required The resource file which contains the elsql SQL statements to use. You can specify multiple resources separated by comma. The resources are loaded on the classpath by default, you can prefix with file: to load from file system. Notice you can set this option on the component and then you do not have to configure this on the endpoint. |
elSqlConfig | | null | To use a specific configured ElSqlConfig. It may be better to use the databaseVendor option instead. |
databaseVendor | | Default | To use a vendor specific ElSqlConfig. The possible values are: Default, Postgres, HSql, MySql, Oracle, SqlServer2008, Veritca |
batch
| boolean
| false
| Execute SQL batch update statements. See notes below on how the treatment of the inbound message body changes if this is set to true . |
dataSource
| String
| null
| Reference to a DataSource to look up in the registry. |
template.<xxx>
| | null
| Sets additional options on the Spring NamedParameterJdbcTemplate that is used behind the scenes to execute the queries. For instance, template.maxRows=10 . For detailed documentation, see the NamedParameterJdbcTemplate javadoc documentation. |
consumer.delay
| long
| 500
| Delay in milliseconds between each poll. |
consumer.initialDelay
| long
| 1000
| Milliseconds before polling starts. |
consumer.useFixedDelay
| boolean
| false
| Set to true to use fixed delay between polls, otherwise fixed rate is used. See ScheduledExecutorService in JDK for details. |
maxMessagesPerPoll
| int
| 0
| An integer value to define the maximum number of messages to gather per poll. By default, no maximum is set. |
consumer.useIterator
| boolean
| true
| If true each row returned when polling will be processed individually. If false the entire java.util.List of data is set as the IN body. |
consumer.routeEmptyResultSet
| boolean
| false
| Whether to route a single empty Exchange if there was no data to poll. |
consumer.onConsume
| String
| null
| 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
| 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
| After processing the entire batch, this query can be executed to bulk update rows etc. The query cannot have parameters. |
consumer.breakBatchOnConsumeFail
| boolean
| false
| 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. |
outputType
| String
| SelectList
| Make the output of consumer or producer to SelectList as List of Map, or SelectOne as single Java object in the following way: a) If the query has only single column, then that JDBC Column object is returned. (such as SELECT COUNT( * ) FROM PROJECT will return a Long object. b) If the query has more than one column, then it will return a Map of that result. c) If the outputClass is set, then it will convert the query result into an Java bean object by calling all the setters that match the column names. It will assume your class has a default constructor to create instance with. d) If the query resulted in more than one rows, it throws an non-unique result exception. Tthe SelectList also supports mapping each row to a Java object as the SelectOne does (only step c). |
outputClass
| String
| null
| Specify the full package and class name to use as conversion when outputType=SelectOne . |
outputHeader
| String | null | To store the result as a header instead of the message body. This allows to preserve the existing message body as-is. |
noop
| boolean
| false
| 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 |