...
c> There are a set of nice processors to the camel-cache component to provide the ability to perform cache lookups and selectively replace payload content at the
- body
- token
- xpath level
Warning |
---|
The Cache consumer is an event based consumer and can be used to listen and respond to specific cache activities. If you need to perform selections from a pre-existing cache, used the processors defined for the cache component. |
URI format
Code Block |
---|
cache:cacheName[?options] |
...
Name | Default Value | Description | |||
---|---|---|---|---|---|
| | The numer of elements that may be stored in the defined cache | |||
| | The number of elements that may be stored in the defined cache. Options include
| |||
| | Specifies whether cache may overflow to disk | |||
| | Sets whether elements are eternal. If eternal, timeouts are ignored and the | |||
| | The maximum time between creation time and when an element expires. | |||
| | The maximum amount of time between accesses before an element expires | |||
| | Whether the disk store persists between restarts of the Virtual Machine. | |||
| | The number of seconds between runs of the disk expiry thread. The default value | |||
| | The numer of elements that may be stored in the defined cache | | | The default maximum number of rows that can be read by a polling query. The default value is 2000 for Camel 1.5.0 or older. In newer releases the default value is 0. |
Result
The result is returned in the OUT body as an ArrayList<HashMap<String, Object>>
. The List
object contains the list of rows and the Map
objects contain each row with the String
key as the column name.
...