You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 3, 2022. It is now read-only.
So in my case newValue == initialValue but it should still do a put as the value was modified. Maybe if it's using copyOnRead/copyOnWrite it should always put the value? Or is there something I missed/another way I can force an update (besides actually creating a new Value object which I'd rather not do).
The text was updated successfully, but these errors were encountered:
Hey Patrick,
This is indeed a bug, the implementation should reput as soon as .setValue was invoked indeed.
I'll work on fixing this... Thanks for report this!
Alex
alexsnaps
added a commit
to alexsnaps/ehcache-jcache
that referenced
this issue
Dec 9, 2014
I use a cache configured with
In the processor the code looks more or less like this:
after this, the cache remains unchanged.
Looking at the code it's easy to see why
in JCache, line 884
So in my case newValue == initialValue but it should still do a put as the value was modified. Maybe if it's using copyOnRead/copyOnWrite it should always put the value? Or is there something I missed/another way I can force an update (besides actually creating a new Value object which I'd rather not do).
The text was updated successfully, but these errors were encountered: