[
https://issues.jboss.org/browse/ISPN-7954?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on ISPN-7954:
-----------------------------------
Last used set to current time does not sound too useful, unless you have some aversion
against calling System.currentTimeMillis() directly :) I would rather provide last access
time and update that only after that. If it's not too much fuss.
Cache.getCacheEntry clears created/lastUsed times before returning
------------------------------------------------------------------
Key: ISPN-7954
URL:
https://issues.jboss.org/browse/ISPN-7954
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 9.0.1.Final, 9.1.0.Beta1
Reporter: William Burns
While writing a test for ISPN-7952 I found that due to the layers of wrapping and
transformations of cache entry objects that the created and last used times will get
cleared and set to 0. Do we care about user getting this data, and actually lastUsed would
probably be the current time as it was just accessed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)