Hi,
I have a system, where I want to invalidate the cache for a record after a update.
I have tried to set the invalidate cache on the operation type in my ds.xml:
When I do this, my SmartGwt console RPC log no longer returns the data. I.e, DSResponse.getData() returns null when I expected it to return the newly updated record.
Is this the intended behaviour, or is this a bug? If I remove the invalidate cache setting, data is returned normally.
This causes problems, if I use the update in a queued update, because I´m unable to find the identity of the newly updated record in my velocity expression in the datasource:
i.e. $responseData.last('dsname','update').id is null.
SmartGWT Poweredition 2014-04-26
Rolf
I have a system, where I want to invalidate the cache for a record after a update.
I have tried to set the invalidate cache on the operation type in my ds.xml:
Code:
<operationBinding operationType="update" invalidateCache="true"/>Is this the intended behaviour, or is this a bug? If I remove the invalidate cache setting, data is returned normally.
This causes problems, if I use the update in a queued update, because I´m unable to find the identity of the newly updated record in my velocity expression in the datasource:
i.e. $responseData.last('dsname','update').id is null.
SmartGWT Poweredition 2014-04-26
Rolf