...
Camel ships with a support implementation of org.apache.camel.component.dataset.DataSet, the org.apache.camel.component.dataset.DataSetSupport class, that can be used as a base for implementing your own DataSet. Camel also ships with some implementations that can be used for testing: org.apache.camel.component.dataset.SimpleDataSet, org.apache.camel.component.dataset.ListDataSet and org.apache.camel.component.dataset.FileDataSet, all of which extend DataSetSupport.
Options
| Div |
|---|
| class | confluenceTableSmall |
|---|
|
Option | Default | Description |
|---|
produceDelay
| 3
| Allows a delay in ms to be specified, which causes producers to pause in order to simulate slow producers. Uses a minimum of 3 ms delay unless you set this option to to -1 to force no delay at all. | consumeDelay
| 0
| Allows a delay in ms to be specified, which causes consumers to pause in order to simulate slow consumers. | preloadSize
| 0
| Sets how many messages should be preloaded (sent) before the route completes its initialization. | initialDelay
| 1000
| Camel 2.1: Time period in millis to wait before starting sending messages. | minRate
| 0
| Wait until the DataSet contains at least this number of messages | dataSetIndex | lenient | Camel 2.17: Controls the behavior of the the CamelDataSetIndex header. The supported values are: , and . The default behavior prior to Camel 2.17 can be restored using dataSetIndex=strict. | Client Type | DataSet Index Value | Description |
|---|
| Consumer | strict | The CamelDataSetIndex header will always be set. | | | lenient | | | off | The CamelDataSetIndex header will NOT be set. | | Producer | strict | The CamelDataSetIndex header must be present and the value of the header will be verified. | | | lenient | If the CamelDataSetIndex header is present, the value of the header will be verified. If the header is not present, it will be set. | | | off | If the CamelDataSetIndex header is present, the value of the header will not be verified. If the header is not present, it will not be set. |
For consumers:
- strict or lenient => The The CamelDataSetIndex header will always be set
- off => The The CamelDataSetIndex header will not be set For producers:
- strict => The The CamelDataSetIndex header must be present and the value of the header will be verified
- lenient => If the the CamelDataSetIndex header is present, the value of the header will be verified. If the header is not present, it will be set.
- off => If the the CamelDataSetIndex header is present, the value of the header will not be verified. If the header is not present, it will not be set. |
|
...
