When configured to storeByValue, keys should be stored by value about ehcache-jcache HOT 3 CLOSED

Ryan

Can you create an issue for this in the project. I will get the Terracotta Engineers to add the missing functionality to Ehcache core.

On 09/11/2011, at 12:42 AM, Ryan Gardner wrote:

Currently the StoreByValueTest#get_existing_MutateKey() and StoreByValueTest#getAndPut_Existing_NonSameKey_MutateKey tests in the TCK fail

---

Reply to this email directly or view it on GitHub:
#3

Regards

Greg Luck

web: http://gregluck.com
skype: gregrluck
yahoo: gregrluck
mobile: +61 408 061 622

from ehcache-jcache.

I opened an issue here:

https://jira.terracotta.org/jira/browse/EHC-891

and migrated the TCK test that is failing into a test case that only uses
Ehcache so hopefully the engineer looking at it will be able to look into
it quickly.

Ryan
On Nov 8, 2011 7:43 PM, "Greg Luck" <
[email protected]>
wrote:

Ryan

Can you create an issue for this in the project. I will get the Terracotta
Engineers to add the missing functionality to Ehcache core.

On 09/11/2011, at 12:42 AM, Ryan Gardner wrote:

Currently the StoreByValueTest#get_existing_MutateKey() and
StoreByValueTest#getAndPut_Existing_NonSameKey_MutateKey tests in the TCK
fail

---

Reply to this email directly or view it on GitHub:
#3

Regards

Greg Luck

web: http://gregluck.com
skype: gregrluck
yahoo: gregrluck
mobile: +61 408 061 622

---

Reply to this email directly or view it on GitHub:
#3 (comment)

from ehcache-jcache.

In the JCache adapter layer, I now have it clone the key if the cache is set up to storeByValue before it creates the Element that gets stored in the ehcache. (I tried using a custom copy strategy, but the key is not read out of the Element returned from the CopyOnWrite strategy - so I had to clone it further up the stream)

from ehcache-jcache.