THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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 |
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.
Sending/Receiving Messages to/from the cache
Sending data to the cache involves setting the Message Exchange Headers given in the section belowNote: This component fetches ResultSetMetaData to be able to return the column name as the key in the Map.
Message Headers
Header | Description |
|---|---|
| If the query is a |
| If the query is an |
| The operation to be performed on the cache. The valid options are
|
| The cache key used to store the Message in the cache. The cache key is optional if the CACHE_OPERATION is DELETEALL |
Cache Producer Samples
In the following example, we fetch the rows from the customer table.
...